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 bethard, docs@python, guilherme-pg, r.david.murray, v+python
Date 2012-03-10.00:04:11
SpamBayes Score 0.00032970536
Marked as misclassified No
Message-id <>
Sad.  That means all the documentation of workarounds needs to be written, even figured out in the first place.  Steven's code, while being a nice implementation when proper arguments are provided, produces inappropriate errors, because only the positional, or only the optional, parameters are printed when errors occur.

So it would probably take a third parser, with all the parameters defined, to exist, to allow easiest generation of the usage message, but I'm not quite sure how to catch the error printing, and redirect it to the third parser.

So, I tried the classes in; they are not complete; CompatibleArgumentParser should pass through all the other APIs, and I'm not sure if all the extension semantics can be appropriately passed through when there are three classes and two objects involved.  But this is sort of a proof-of-concept wrapper for achieving intermixed optional and positional arguments, and still get proper error messages.
Date User Action Args
2012-03-10 00:04:12v+pythonsetrecipients: + v+python, bethard, r.david.murray, docs@python, guilherme-pg
2012-03-10 00:04:12v+pythonsetmessageid: <>
2012-03-10 00:04:11v+pythonlinkissue14191 messages
2012-03-10 00:04:11v+pythoncreate