[issue6253] optparse.OptionParser.get_usage uses wrong formatter

Change by Irit Katriel : -- stage: -> resolved status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue6253] optparse.OptionParser.get_usage uses wrong formatter

Irit Katriel added the comment: optparse is deprecated an no longer in development, so unless someone objects I will close this issue. -- resolution: -> wont fix status: open -> pending ___ Python tracker _

[issue6253] optparse.OptionParser.get_usage uses wrong formatter

Irit Katriel added the comment: Jan, if you are still interested in fixing this you would need to add a test to the patch. -- nosy: +iritkatriel versions: +Python 3.10, Python 3.8, Python 3.9 -Python 2.6 ___ Python tracker

[issue6253] optparse.OptionParser.get_usage uses wrong formatter

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue6253] optparse.OptionParser.get_usage uses wrong formatter

Mark Lawrence added the comment: Is it worth leaving this open as optparse was deprecated in 2.7 in favour of argparse? -- components: +Library (Lib) -Extension Modules nosy: +BreamoreBoy ___ Python tracker ___

[issue6253] optparse.OptionParser.get_usage uses wrong formatter

Sandro Tosi added the comment: Jan, are you still interested in this? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue6253] optparse.OptionParser.get_usage uses wrong formatter

Sandro Tosi added the comment: Hello Jan, I noticed this bug and I wondered: what's your opinion now? Optparse is deprecated and it will be replaced by argparse, so I'm not sure it's "interesting" to introduce a new feature (the format_usage() method) but it might still be interesting to fix

[issue6253] optparse.OptionParser.get_usage uses wrong formatter

Changes by Jan Pobrislo : Added file: http://bugs.python.org/file14257/fix_optparse_usage_formatter2.diff ___ Python tracker ___ ___ Python-bug

[issue6253] optparse.OptionParser.get_usage uses wrong formatter

Changes by Jan Pobrislo : Removed file: http://bugs.python.org/file14256/fix_optparse_usage_formatter2.diff ___ Python tracker ___ ___ Python-

[issue6253] optparse.OptionParser.get_usage uses wrong formatter

Jan Pobrislo added the comment: On second thought method name starting with get_ doesn't signify any formatting, so it might be better to either: 1) Move call to formatter.format_usage from get_usage directly to format_help. 2) Create method format_usage in OptionParser and call it from there.

[issue6253] optparse.OptionParser.get_usage uses wrong formatter

Changes by Jan Pobrislo : Removed file: http://bugs.python.org/file14254/fix_optparse_usage_formatter.diff ___ Python tracker ___ ___ Python-bu

[issue6253] optparse.OptionParser.get_usage uses wrong formatter

Changes by Jan Pobrislo : Added file: http://bugs.python.org/file14255/fix_optparse_usage_formatter.diff ___ Python tracker ___ ___ Python-bugs

[issue6253] optparse.OptionParser.get_usage uses wrong formatter

New submission from Jan Pobrislo : When using OptionParser.format_help(formatter), the formatter parameter should be used to format all of the help message. This is not the case for usage message, as the method get_usage() is not passed the formatter and always uses self.formatter. I'm using pyth