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 rhettinger
Recipients monkeyman79, paul.j3, r.david.murray, rhettinger, v+python
Date 2021-01-28.06:32:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Sounds like another wet blanket argpment

Please watch your tone.  It borders on being abusive.

It is entirely appropriate to set limits on the scope of what a module is trying to achieve.  It is appropriate to consider module learnability.  It is appropriate to limit sprawl and feature creep.  It is appropriate to consider whether the pattern being encouraged and supported by the PR is intellectually manageable by end users.

It is correct that argparse set out to handle more complex cases than optparse.  But even then, it was aiming to cases that commonly arose it the wild (subparsers are not uncommon).  It never aspired to be all things to all users.
Date User Action Args
2021-01-28 06:32:05rhettingersetrecipients: + rhettinger, v+python, r.david.murray, paul.j3, monkeyman79
2021-01-28 06:32:05rhettingersetmessageid: <>
2021-01-28 06:32:05rhettingerlinkissue43046 messages
2021-01-28 06:32:01rhettingercreate