Bryan <bhlaw...@gmail.com> added the comment:
This sort of ambiguity is why I like strongly typed languages and languages where timtoady is not seen often. I can guarantee you, that if argparse was implemented in Pascal (and copt most probably has been), that if type was specified and a default given, that the default would have to adhere to that type. It is just programming common sense.... On Wed, 24 Jun 2020 02:20 paul j3, <rep...@bugs.python.org> wrote: > > paul j3 <ajipa...@gmail.com> added the comment: > > 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. > > ---------- > > _______________________________________ > Python tracker <rep...@bugs.python.org> > <https://bugs.python.org/issue41087> > _______________________________________ > ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue41087> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
