Message170404
| Author |
chris.jerdonek |
| Recipients |
Arfrever, arnau, barry, benjamin.peterson, bethard, chris.jerdonek, georg.brandl, python-dev, r.david.murray |
| Date |
2012年09月12日.17:01:42 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1347469303.54.0.58691424901.issue15906@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> Do we need a new test for conversion of string defaults?
I think we should also update the documentation of the "default" keyword argument (and/or the "type" argument) to remove any ambiguity and make the behavior more clear.
Maybe one way to view what is happening (and maybe one way to describe it in the documentation) is that if a default value is a string, the parser treats it as a default for the command-line *argument*, otherwise it treats it as a default for the final *attribute*.
Lastly, can we also add the test from one of my first comments above to check that "double conversion" of strings doesn't take place? |
|