Message 144484 - Python tracker

Author	bewest
Recipients	G2P, bethard, bewest, csernazs, dsully, elsdoerfer, eric.araujo, nvie, r.david.murray
Date	2011-09-24.06:55:32
SpamBayes Score	8.83217e-08
Marked as misclassified	No
Message-id	<1316847333.75.0.956948517947.issue9253@psf.upfronthosting.co.za>
In-reply-to

Content
I spent some time looking at this, as I was interested in using this pattern to simulate what git and hg do. I considered a few modifications and then found this bug. I think the default keyword passed to _SubParsersAction.__init__ makes sense. I started on a patch, that looks promising, but I'm having trouble getting the regexp right. Here's a changeset higlighting where I think the problematic regexp is: https://bitbucket.org/bewest/argparse/changeset/938e1e91ddd0 https://gist.github.com/1202975#file_test_opt_subcommand.py Is the meager little test I put together.

I spent some time looking at this, as I was interested in
using this pattern to simulate what git and hg do.  I
considered a few modifications and then found this bug.  I
think the default keyword passed to
_SubParsersAction.__init__ makes sense.

I started on a patch, that looks promising, but I'm having
trouble getting the regexp right.

Here's a changeset higlighting where I think the
problematic regexp is:
https://bitbucket.org/bewest/argparse/changeset/938e1e91ddd0

https://gist.github.com/1202975#file_test_opt_subcommand.py
Is the meager little test I put together.

History
Date	User	Action	Args
2011-09-24 06:55:34	bewest	set	recipients: + bewest, csernazs, bethard, eric.araujo, r.david.murray, nvie, elsdoerfer, G2P, dsully
2011-09-24 06:55:33	bewest	set	messageid: <1316847333.75.0.956948517947.issue9253@psf.upfronthosting.co.za>
2011-09-24 06:55:33	bewest	link	issue9253 messages
2011-09-24 06:55:32	bewest	create