Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #35650 > unrolled thread
| Started by | "Joseph L. Casale" <jcasale@activenetwerx.com> |
|---|---|
| First post | 2012-12-27 20:47 +0000 |
| Last post | 2012-12-27 20:47 +0000 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
RE: Function Parameters "Joseph L. Casale" <jcasale@activenetwerx.com> - 2012-12-27 20:47 +0000
| From | "Joseph L. Casale" <jcasale@activenetwerx.com> |
|---|---|
| Date | 2012-12-27 20:47 +0000 |
| Subject | RE: Function Parameters |
| Message-ID | <mailman.1366.1356641342.29569.python-list@python.org> |
> Don't use kwargs for this. List out the arguments in the function > spec and give the optional ones reasonable defaults. > I only use kwargs myself when the set of possible arguments is dynamic > or unknown. Gotch ya, but when the inputs to some keywords are similar, if the function is called with two of three (which is valid) and the arg name isn't used, the assignment is order dependent and arbitrary in a sense and I can not distinguish. It would be nice if you could force the keyword to be mandatory to forgo the assumption in assignment like kwargs provides with gets. I suppose all the time wasted here is in vain as the caller could blunder elsewhere... Thanks, jlc
Back to top | Article view | comp.lang.python
csiph-web