This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

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 <>
> 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?
Date User Action Args
2012-09-12 17:01:43chris.jerdoneksetrecipients: + chris.jerdonek, barry, georg.brandl, bethard, benjamin.peterson, Arfrever, r.david.murray, arnau, python-dev
2012-09-12 17:01:43chris.jerdoneksetmessageid: <>
2012-09-12 17:01:43chris.jerdoneklinkissue15906 messages
2012-09-12 17:01:42chris.jerdonekcreate