the right way of handling **args for __init__ and other methods
David Bolen
db3l at fitlinxx.com
Mon Jul 24 14:43:35 EDT 2000
More information about the Python-list mailing list
Mon Jul 24 14:43:35 EDT 2000
- Previous message (by thread): mapping the read() fonction
- Next message (by thread): the right way of handling **args for __init__ and other methods
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Bjorn Pettersen <bjorn at roguewave.com> writes: > Since args looks to be always empty when argdict != None, you can say > > args.update(argdict) If in fact the use of args and argdict are mutually exclusive and argdict is only around for passing on from __init__ then it would seem that you could also just re-assign args, e.g.,: if argdict: args = argdict (although I think the apply() approach is probaby cleaner since it avoids the use of the extra argument to read()). -- -- David -- /-----------------------------------------------------------------------\ \ David Bolen \ E-mail: db3l at fitlinxx.com / | FitLinxx, Inc. \ Phone: (203) 708-5192 | / 860 Canal Street, Stamford, CT 06902 \ Fax: (203) 316-5150 \ \-----------------------------------------------------------------------/
- Previous message (by thread): mapping the read() fonction
- Next message (by thread): the right way of handling **args for __init__ and other methods
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list