[issue4318] optparse: formatting of help text/descriptions

A.M. Kuchling added the comment: I have no idea. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue4318] optparse: formatting of help text/descriptions

Éric Araujo added the comment: amk: could you say if this applies to argparse? -- ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue4318] optparse: formatting of help text/descriptions

Éric Araujo added the comment: optparse is not being developed anymore. -- nosy: +eric.araujo resolution: -> rejected stage: -> committed/rejected status: open -> closed ___ Python tracker

[issue4318] optparse: formatting of help text/descriptions

David W. Lambert added the comment: granted, this isn't terribly difficult: '\n'.join(textwrap.fill(line) for line in text.split('\n')) ___ Python tracker ___ ___

[issue4318] optparse: formatting of help text/descriptions

David W. Lambert added the comment: I'd like textwrap option to preserve new lines. Actual case: I have a code that produces cryptograms meant to be printed and solved with paper and pencil. Standard format for cryptogram inserts space character between each character of the original text,

[issue4318] optparse: formatting of help text/descriptions

Andy Buckley added the comment: FWIW, I would like to see an option on textwrap to preserve newlines for purposes other than optparse formatting. optparse would then just be able to pass that as a flag when building the text wrapper object. Should I open a separate issue targeted at textwrap? -

[issue4318] optparse: formatting of help text/descriptions

New submission from A.M. Kuchling <[EMAIL PROTECTED]>: (Copied from an anonymous submission in the Optik bug tracker.) There have been some recent discussions on comp.lang.python about the optparse/optik module, and Steve Bethard suggested you might be interested in some of the work done there.