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 michelsen
Recipients michelsen
Date 2010-12-11.16:00:44
SpamBayes Score 1.5238633e-10
Marked as misclassified No
Message-id <1292083248.97.0.928495782189.issue10680@psf.upfronthosting.co.za>
In-reply-to
Content
This is a follow-up to Issue 58 from the Google Project Hosting bug tracker (http://code.google.com/p/argparse/issues/detail?id=58). I couldn't find any equivalent/re-posting of it here, so I took the liberty of creating a new one - despite the bug being marked 'WontFix' on Google. The reason for this is that I cannot make the suggested workaround... well, work. 

The root problem: the argparse parser add_mutually_exclusive_group method does not accept title or description arguments. 

The workaround: steven.bethard suggests on google to create a 'straight' dummy group (i.e. one made using the title-accepting add_argument_group method) and then attach the mutually exclusive group to the dummy group - which is attached to the parser itself. 

The problem: while the group does appear as a group with title on the help output, the group does not appear to actually _be_ mutually exclusive (I get no objections to running several arguments from the same group together) nor does it display as mutually exclsuive on the help output. 

Please see attached file for code + resulting output.

(I hope I'm doing this right - this is my first bug report, so bear with and instruct me if I'm getting it wrong)
History
Date User Action Args
2010-12-11 16:00:49michelsensetrecipients: + michelsen
2010-12-11 16:00:48michelsensetmessageid: <1292083248.97.0.928495782189.issue10680@psf.upfronthosting.co.za>
2010-12-11 16:00:44michelsenlinkissue10680 messages
2010-12-11 16:00:44michelsencreate