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 jakub
Recipients bethard, jakub, tshepang
Date 2012-03-19.18:10:15
SpamBayes Score 5.2232585e-06
Marked as misclassified No
Message-id <1332180616.63.0.453952518031.issue14365@psf.upfronthosting.co.za>
In-reply-to
Content
Attached quick&dirty fix I'm currently using in my project. Maybe this will help to create a valid patch.

Instead of changing _parse_optional, I've overridden _get_option_tuples to scan subparsers for matching optional arguments if option is ambiguous in the current parser.

I've only skimmed through the code, so forgive me if that fix is useless.
History
Date User Action Args
2012-03-19 18:10:16jakubsetrecipients: + jakub, bethard, tshepang
2012-03-19 18:10:16jakubsetmessageid: <1332180616.63.0.453952518031.issue14365@psf.upfronthosting.co.za>
2012-03-19 18:10:16jakublinkissue14365 messages
2012-03-19 18:10:15jakubcreate