[issue6454] Add "example" keyword argument to optparse constructor

2010-12-17 Thread Greg Ward
Greg Ward added the comment: > I understood Greg’s reply to mean that there was no need for an examples > keyword if simple paragraph splitting was added. Right, but optparse has been superseded by argparse. So my opinion is even less important than it was before 2.7. -- __

[issue6454] Add "example" keyword argument to optparse constructor

2010-12-16 Thread Éric Araujo
Éric Araujo added the comment: I understood Greg’s reply to mean that there was no need for an examples keyword if simple paragraph splitting was added. -- ___ Python tracker __

[issue6454] Add "example" keyword argument to optparse constructor

2010-12-16 Thread Raymond Hettinger
Raymond Hettinger added the comment: The two principals on the two argument parsing modules both find this unnecessary. -- resolution: -> rejected status: open -> closed ___ Python tracker ___

[issue6454] Add "example" keyword argument to optparse constructor

2010-11-28 Thread Steven Bethard
Steven Bethard added the comment: With argparse, you can specify formatter_class= RawDescriptionHelpFormatter and then format things however you want in the description. http://docs.python.org/dev/library/argparse.html#formatter-class So I think there's no need for this in argparse.

[issue6454] Add "example" keyword argument to optparse constructor

2010-11-27 Thread Éric Araujo
Éric Araujo added the comment: This may be interesting for argparse too. -- nosy: +bethard, eric.araujo ___ Python tracker ___ ___ Pyt

[issue6454] Add "example" keyword argument to optparse constructor

2009-11-22 Thread Greg Ward
Greg Ward added the comment: > but I feel there is a better and more general > solution - just provide some minimal formatting for description: treat > empty line as paragraph separator. Then I would be able to add example > or anything else to the description formatting it as necessary Agreed.

[issue6454] Add "example" keyword argument to optparse constructor

2009-11-19 Thread Marcin Kasperski
Marcin Kasperski added the comment: I found this bug while looking for suggestions how to add examples to the optparse help call, but I feel there is a better and more general solution - just provide some minimal formatting for description: treat empty line as paragraph separator. Then I would b

[issue6454] Add "example" keyword argument to optparse constructor

2009-11-18 Thread Raymond Hettinger
Changes by Raymond Hettinger : -- assignee: rhettinger -> gward nosy: +gward ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue6454] Add "example" keyword argument to optparse constructor

2009-09-24 Thread Raymond Hettinger
Raymond Hettinger added the comment: This seems like a reasonable request. -- assignee: -> rhettinger nosy: +rhettinger ___ Python tracker ___ __

[issue6454] Add "example" keyword argument to optparse constructor

2009-07-09 Thread Daniel Waylonis
Daniel Waylonis added the comment: Looking at the source, there's the undocumented "epilog" keyword, but it, unfortunately is automatically pushed through the formatter, which would not be desirable for the output. -- ___ Python tracker

[issue6454] Add "example" keyword argument to optparse constructor

2009-07-09 Thread Daniel Waylonis
New submission from Daniel Waylonis : It's useful to see and example or two detailing how a program should be invoked and the expected results. I'd like to add the "example" keyword which will be printed below the "options:" when the usage is displayed. It would not be formatted like the "de