[issue4278] optparse quirks

2009-07-01 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc added the comment: - For the -h option, you may add "add_help_option=False" when creating the Optparse object - concerning the error message: every parser that tries to give meaningful error messages has to guess what the user really meant. The exact text is really an imple

[issue4278] optparse quirks

2009-02-26 Thread Andy Buckley
Andy Buckley added the comment: Are these really bugs? The first message just reports the error the other way around from how you view it: you are thinking of "-TO" as a two-character "short option", optparse thinks of it as a two-character long option which is missing a dash. I would side with

[issue4278] optparse quirks

2008-12-10 Thread Martin v. Löwis
Martin v. Löwis <[EMAIL PROTECTED]> added the comment: No patch proposed yet, so retargetting to trunk. -- nosy: +loewis versions: +Python 2.7 -Python 2.5.3 ___ Python tracker <[EMAIL PROTECTED]>

[issue4278] optparse quirks

2008-11-07 Thread Keith Briggs
New submission from Keith Briggs <[EMAIL PROTECTED]>: I got the message: optparse.OptionError: invalid long option string '-T0': must start with --, followed by non-dash This is bad - the real error was that I gave a short option which did not have a single letter. Also, it seems that add_opti