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 r.david.murray
Recipients cmcqueen1975, eric.araujo, ezio.melotti, r.david.murray
Date 2010-07-05.15:52:48
SpamBayes Score 0.000288952
Marked as misclassified No
Message-id <>
Too bad you didn't find this on one of the RCs.  The fix will have to wait for 2.7.1 now.

The line you originally quote as changing was, as far as I can tell, the original code (it enters our repository on 2006-04-22 in r45654 when optparse was upgraded to version 1.5.1 of optik).  The change to the plural form in that line was made for 2.6rc1 in r71345, possibly inadvertently since that changeset was the bump to rc1.

It would seem reasonable to change this to match 2.6 for 2.7.1, since as far as I know no bugs have been reported against it in 2.6, and it is unlikely to break working code in 2.7.

As for the more extensive problems, now that argparse is part of the standard library it would seem better to devote any development resources to it.  Can you test your issues against argparse, and open a new issue if it also has problems?
Date User Action Args
2010-07-05 15:52:51r.david.murraysetrecipients: + r.david.murray, ezio.melotti, eric.araujo, cmcqueen1975
2010-07-05 15:52:51r.david.murraysetmessageid: <>
2010-07-05 15:52:49r.david.murraylinkissue9161 messages
2010-07-05 15:52:48r.david.murraycreate