Bryan <bhlaw...@gmail.com> added the comment:
Maybe so, But, the issue is, if it trips up a user when they try to use the option, it should trip up the dev when the default is used... On Tue, 23 Jun 2020 18:47 Karthikeyan Singaravelan, <rep...@bugs.python.org> wrote: > > Karthikeyan Singaravelan <tir.kar...@gmail.com> added the comment: > > There is a documentation note on type casting along with an example > similar to the report > https://docs.python.org/3.8/library/argparse.html#default > > > If the default value is a string, the parser parses the value as if it > were a command-line argument. In particular, the parser applies any type > conversion argument, if provided, before setting the attribute on the > Namespace return value. Otherwise, the parser uses the value as is: > > ---------- > nosy: +paul.j3, rhettinger, xtreak > type: -> behavior > > _______________________________________ > 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
