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 v+python
Recipients monkeyman79, paul.j3, r.david.murray, rhettinger, v+python
Date 2021-01-28.05:24:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Raymond said:
ISTM the scope of argparse was never intended to capture all possible patterns for command line argument parsing.  Instead, it aimed at to address the common cases.

I say:
Sounds like another wet blanket argpment. Refer to the section "Why aren't getopt and optparse enough?" in the argparse PEP 389.  It is clearn that argparse was intended to implement more complex cases than could be easily implemented with the prior getopt and optparse. The concepts of variable numbers of arguments for an option, and of subcommonds, introduced initially in argparse, are far more complex than the enhancements proposed here.
Date User Action Args
2021-01-28 05:24:46v+pythonsetrecipients: + v+python, rhettinger, r.david.murray, paul.j3, monkeyman79
2021-01-28 05:24:46v+pythonsetmessageid: <>
2021-01-28 05:24:46v+pythonlinkissue43046 messages
2021-01-28 05:24:46v+pythoncreate