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 paul.j3
Recipients Bryan, paul.j3, rhettinger, xtreak
Date 2020-06-23.16:20:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1592929244.92.0.656168653058.issue41087@roundup.psfhosted.org>
In-reply-to
Content
No, parameters like `type` let the developer control what his users provides.  Violating that produces a runtime error, and exit.

But in general argparse does not try to control values that the developer uses.  There's plenty of time during development to catch error such as this - if they are errors at all.  

'type' does not 'declare' what the attribute will be.  It is a function that is applied to the input string, and converts that to something or other, or raises a TypeError.  It is used only if there is a string value to work on, either from the user, or a string default.  

This is not a bug, so should be closed.
History
Date User Action Args
2020-06-23 16:20:44paul.j3setrecipients: + paul.j3, rhettinger, xtreak, Bryan
2020-06-23 16:20:44paul.j3setmessageid: <1592929244.92.0.656168653058.issue41087@roundup.psfhosted.org>
2020-06-23 16:20:44paul.j3linkissue41087 messages
2020-06-23 16:20:44paul.j3create