Author bethard
Recipients Kotan, bethard, catherine, elsdoerfer, eric.araujo, wrobell
Date 2012-07-23.16:57:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1343062656.57.0.954605325792.issue9338@psf.upfronthosting.co.za>
In-reply-to
Content
So Kotan's patch doesn't actually solve the original problem. Instead, it inserts the workaround into the help message of the parser. I think this is probably not the right fix. We should probably do two things:

(1) Right now: create a documentation patch which at least explains the current limitations of argparse parsing, and describes the '--' workaround. Probably this patch should add a separate section about '--', give an example like the one in this issue, and then cross-reference this section from nargs='?', nargs='*', nargs='+' and the "Arguments containing -" section.

(2) Longer term: create a code patch that implements the changes to the regular expression-based parsing like I've suggested.
History
Date User Action Args
2012-07-23 16:57:36bethardsetrecipients: + bethard, wrobell, eric.araujo, catherine, elsdoerfer, Kotan
2012-07-23 16:57:36bethardsetmessageid: <1343062656.57.0.954605325792.issue9338@psf.upfronthosting.co.za>
2012-07-23 16:57:35bethardlinkissue9338 messages
2012-07-23 16:57:35bethardcreate