[issue9399] Provide a 'print' action for argparse

Raymond Hettinger added the comment: Marking this as closed because there has been no activity or interest for over five years. If anyone wants to revive this and write a PR, feel free to reopen. The core idea is plausible, but this doesn't seem to be a recurring need. -- resolutio

[issue9399] Provide a 'print' action for argparse

Change by Raymond Hettinger : -- assignee: bethard -> rhettinger nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list mailin

[issue9399] Provide a 'print' action for argparse

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

[issue9399] Provide a 'print' action for argparse

paul j3 added the comment: As Steven notes, the patch lacks tests. It also lacks documentation. The 2 things that this class does different from 'version' are - write without passing the text through 'textwrap' - write to a user defined file There is a difference in opinion between Éric and

[issue9399] Provide a 'print' action for argparse

Changes by Berker Peksag : -- nosy: +berker.peksag ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue9399] Provide a 'print' action for argparse

Mark Lawrence added the comment: @Paul what is your take on this, other opinions seem positive? -- nosy: +BreamoreBoy, paul.j3 versions: +Python 3.5 -Python 3.3 ___ Python tracker ___

[issue9399] Provide a 'print' action for argparse

Changes by Denilson Figueiredo de Sá : -- nosy: +denilsonsa ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue9399] Provide a 'print' action for argparse

Steven Bethard added the comment: Argparse's wrapping behavior is determined by the formatter_class: http://docs.python.org/library/argparse.html#formatter-class Is it reasonable to assume that if you're wrapping your own messages you're already specifying formatter_class=argparse.RawTextHelp

[issue9399] Provide a 'print' action for argparse

Éric Araujo added the comment: Thanks for the new patch. It does not apply cleanly to the py3k branch, but that’s very easily corrected. self.file.write(self.message) self.file.write('\n') Could be replaced by print(self.message, file=self.file) print will use the r

[issue9399] Provide a 'print' action for argparse

Dennis Malcorps added the comment: I totally forgot about this patch, sorry... Due to university and another python project I am working on I didn't find the time to look at the test suite. I would really appreciate it if someone else could do this ;-) Anyway, I added the changes proposed by

[issue9399] Provide a 'print' action for argparse

Éric Araujo added the comment: Thinking again about that, what’s wrong with argparse replacing \n with spaces and doing its own line wrapping? -- versions: +Python 3.3 -Python 3.2 ___ Python tracker __

[issue9399] Provide a 'print' action for argparse

Éric Araujo added the comment: sys.std* should not be used as default values in a function definition, because they may be rebound to other objects. The usual idiom is to have None as default value and check it at call time. The patch also needs tests and docs. (FTR, the example for callabl

[issue9399] Provide a 'print' action for argparse

Steven Bethard added the comment: The patch looks basically right. A few minor issues: * "message=None," should probably be "message,", that is, message should not be allowed to default to None - I can't see any use case for this action without a message. I believe this means the body of __ca

[issue9399] Provide a 'print' action for argparse

Dennis Malcorps added the comment: Here is a patch that adds a 'write' action to argparse. Usage example: >>> parser = argparse.ArgumentParser() >>> parser.add_argument("--license", action="write", message="This file\nis >>> licensed under \t GPL") >>> parser.parse_args(['--license']) This fil

[issue9399] Provide a 'print' action for argparse

Steven Bethard added the comment: The equivalent to optparse callback is basically to define __call__ in a subclass of Action. Pretty much the same amount of work because they both have complicated parameters. The "callable" I (not fully confidently) proposed would just be a shorthand for de

[issue9399] Provide a 'print' action for argparse

Dennis Malcorps added the comment: > parser.add_argument('--license', action='write', message='...', > file=sys.stdout) The ability to redirect the output would be a nice addition. > parser.add_argument('--license', action='call', callable=lambda: > sys.stdout.write(message)) optparse alread

[issue9399] Provide a 'print' action for argparse

Steven Bethard added the comment: Should this print to stdout or stderr? I wonder if the API should allow either, and instead look like: parser.add_argument('--license', action='write', message='...', file=sys.stdout) Where sys.stdout would be the default for the file= argument. The action wo

[issue9399] Provide a 'print' action for argparse

Georg Brandl added the comment: Sounds like a good addition to me. -- assignee: -> bethard nosy: +georg.brandl ___ Python tracker ___ ___

[issue9399] Provide a 'print' action for argparse

Changes by R. David Murray : -- nosy: +bethard versions: -Python 2.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscr

[issue9399] Provide a 'print' action for argparse

New submission from Dennis Malcorps : Currently argparse has a 'version' action which can be triggered by user defined options which prints out a custom string. parser.add_argument("--version", action="version", version="test 1.2.3") Since the 'version' action can be added multiple times, it c