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 amcnabb, bethard, docs@python, guilherme-pg, paul.j3, r.david.murray, v+python
Date 2013-04-18.17:14:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1366305281.81.0.0697370278189.issue14191@psf.upfronthosting.co.za>
In-reply-to
Content
Paul, your comments are interesting, but your proposed patch doesn't actually solve the problem.

So here I am typing away at my command prompt, and I type in a couple optional parameters I know I'll need and start on the sequence of positional ones, and half way through I remember "oh, I need another optional paremeter" so I type it in next before I forget, and then go on with the positional ones.

No prior Unix-style argument parsing mechanism that I have ever seen or heard of would be confused by that, but argparse is.

This bug is about providing a facility in argparse that supports intermixing optional parameters into strings of positional parameters, just like all prior Unix-style argument parsing mechanisms, so that an application can be ported to use argparse without breaking command lines that their users have stored in command files. Otherwise argparse is not an upgrade path for an application, yet optparse has been deprecated.
History
Date User Action Args
2013-04-18 17:14:41v+pythonsetrecipients: + v+python, amcnabb, bethard, r.david.murray, docs@python, paul.j3, guilherme-pg
2013-04-18 17:14:41v+pythonsetmessageid: <1366305281.81.0.0697370278189.issue14191@psf.upfronthosting.co.za>
2013-04-18 17:14:41v+pythonlinkissue14191 messages
2013-04-18 17:14:41v+pythoncreate