Message155008
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. |
|
Date |
User |
Action |
Args |
2012-03-06 09:34:26 | bethard | set | recipients:
+ bethard, v+python |
2012-03-06 09:34:26 | bethard | set | messageid: <1331026466.56.0.914808458774.issue14191@psf.upfronthosting.co.za> |
2012-03-06 09:34:25 | bethard | link | issue14191 messages |
2012-03-06 09:34:25 | bethard | create | |
|