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 andersk
Recipients andersk, bethard, drm, eric.araujo, eric.smith, gdb, nelhage, r.david.murray
Date 2011-02-06.19:53:43
SpamBayes Score 1.6462976e-05
Marked as misclassified No
Message-id <1297022024.61.0.205609489102.issue9334@psf.upfronthosting.co.za>
In-reply-to
Content
That would be a good first step.

I continue to advocate making that mode the default, because it’s consistent with how every other command line program works[1], and backwards compatible with the current argparse behavior.

As far as documentation for older versions, would it be reasonable to un-deprecate optparse until argparse becomes a suitable replacement?  There are still lots of programmers working in Python 2.7.

[1] bethard’s msg128047 is confusing positional arguments with option arguments.  All UNIX commands that accept option arguments have no trouble accepting option arguments that begin with -.  For example, ‘grep -e -pattern file’ is commonly used to search for patterns beginning with -.
History
Date User Action Args
2011-02-06 19:53:44andersksetrecipients: + andersk, bethard, eric.smith, eric.araujo, r.david.murray, gdb, nelhage, drm
2011-02-06 19:53:44andersksetmessageid: <1297022024.61.0.205609489102.issue9334@psf.upfronthosting.co.za>
2011-02-06 19:53:44andersklinkissue9334 messages
2011-02-06 19:53:43anderskcreate