[issue6253] optparse.OptionParser.get_usage uses wrong formatter

2009-06-10 Thread Jan Pobrislo
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

[issue6253] optparse.OptionParser.get_usage uses wrong formatter

2009-06-10 Thread Jan Pobrislo
Changes by Jan Pobrislo : Added file: http://bugs.python.org/file14255/fix_optparse_usage_formatter.diff ___ Python tracker <http://bugs.python.org/issue6253> ___ ___

[issue6253] optparse.OptionParser.get_usage uses wrong formatter

2009-06-10 Thread Jan Pobrislo
Changes by Jan Pobrislo : Removed file: http://bugs.python.org/file14254/fix_optparse_usage_formatter.diff ___ Python tracker <http://bugs.python.org/issue6253> ___ ___

[issue6253] optparse.OptionParser.get_usage uses wrong formatter

2009-06-10 Thread Jan Pobrislo
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

[issue6253] optparse.OptionParser.get_usage uses wrong formatter

2009-06-10 Thread Jan Pobrislo
Changes by Jan Pobrislo : Removed file: http://bugs.python.org/file14256/fix_optparse_usage_formatter2.diff ___ Python tracker <http://bugs.python.org/issue6253> ___ ___

[issue6253] optparse.OptionParser.get_usage uses wrong formatter

2009-06-10 Thread Jan Pobrislo
Changes by Jan Pobrislo : Added file: http://bugs.python.org/file14257/fix_optparse_usage_formatter2.diff ___ Python tracker <http://bugs.python.org/issue6253> ___ ___