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 bethard
Recipients bethard, v+python
Date 2012-03-06.09:34:25
SpamBayes Score 5.880395e-05
Marked as misclassified No
Message-id <1331026466.56.0.914808458774.issue14191@psf.upfronthosting.co.za>
In-reply-to
Content
This behavior is intentional - positional arguments must be sequential, not broken up with optional (flag) arguments between. So this is a documentation bug.

Allowing positional arguments to be broken up with optional (flag) arguments between them would be a new feature. It would also break many current parsers, so it couldn't be turned on by default. A new constructor parameter or method or something would have to be added to ArgumentParser. Patches welcome.
History
Date User Action Args
2012-03-06 09:34:26bethardsetrecipients: + bethard, v+python
2012-03-06 09:34:26bethardsetmessageid: <1331026466.56.0.914808458774.issue14191@psf.upfronthosting.co.za>
2012-03-06 09:34:25bethardlinkissue14191 messages
2012-03-06 09:34:25bethardcreate