➜

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 kkarbowiak
Recipients Albert White, Jacktose, Martin.d'Anjou, Oliver.Smith, benschmaus, bethard, docs@python, eric.araujo, eric.smith, kkarbowiak, maggyero, markgrandi, martin.panter, mburger, paul.j3, r.david.murray, rhartkopf, rhettinger, shaharg, terry.reedy, tonygaetani, tshepang
Date 2020-07-20.10:23:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1595240629.66.0.91687679094.issue9694@roundup.psfhosted.org>
In-reply-to
Content 
It seems the discussion has so far revolved around 'optional' arguments with `required=True`.

What about the other way around?

While trying to set `required=False` for a positional argument raises an exception, it is still possible to make the positional argument effectively optional by `nargs='?'` (it is then printed in brackets in usage message).
History
Date User Action Args
2020-07-20 10:23:49kkarbowiaksetrecipients: + kkarbowiak, rhettinger, terry.reedy, bethard, eric.smith, eric.araujo, r.david.murray, docs@python, benschmaus, tshepang, martin.panter, paul.j3, markgrandi, mburger, Martin.d'Anjou, Oliver.Smith, rhartkopf, Albert White, tonygaetani, shaharg, maggyero, Jacktose
2020-07-20 10:23:49kkarbowiaksetmessageid: <1595240629.66.0.91687679094.issue9694@roundup.psfhosted.org>
2020-07-20 10:23:49kkarbowiaklinkissue9694 messages
2020-07-20 10:23:49kkarbowiakcreate