[issue18920] argparse module version action

Changes by Eli Bendersky : -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed versions: -Python 3.4 ___ Python tracker ___ ___

[issue18920] argparse module version action

Roundup Robot added the comment: New changeset 587bdb940524 by Eli Bendersky in branch 'default': Update whatsnew/3.4 wrt. --version going to stdout. #18338, #18920, #18922 http://hg.python.org/cpython/rev/587bdb940524 -- ___ Python tracker

[issue18920] argparse module version action

Eli Bendersky added the comment: Thanks, I moved the NEWS entry to the right place. Yes, all tests pass. I'll update whatsnew separately. -- ___ Python tracker ___ _

[issue18920] argparse module version action

Roundup Robot added the comment: New changeset ec9a4b77f37b by Eli Bendersky in branch 'default': Issue #18920: argparse's default version action (for -v, --version) should http://hg.python.org/cpython/rev/ec9a4b77f37b -- nosy: +python-dev ___ Python

[issue18920] argparse module version action

Serhiy Storchaka added the comment: > This might also explain why argparse uses stderr (other modules/scripts in > the stdlib might do the same too). Lib/trace.py, Tools/pynche/Main.py, and Tools/i18n/pygettext.py write to the stdout. Lib/smtpd.py and Tools/i18n/msgfmt.py write to the stderr.

[issue18920] argparse module version action

Serhiy Storchaka added the comment: You misplace Misc/NEWS entry in wrong section -- "What's New in Python 3.4.0 Alpha 1". I think this change (as change of issue18338) worths the mentioning in Doc/whatsnew/3.4.rst. Did you run all test suite? This change can affect other tests. --

[issue18920] argparse module version action

Eli Bendersky added the comment: Patch attached -- keywords: +patch stage: needs patch -> patch review Added file: http://bugs.python.org/file31587/issue18920.1.patch ___ Python tracker

[issue18920] argparse module version action

Eli Bendersky added the comment: The Python executable change is from #18338 -- ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue18920] argparse module version action

Eli Bendersky added the comment: On Wed, Sep 4, 2013 at 6:26 AM, Ezio Melotti wrote: > > Ezio Melotti added the comment: > > Only on 3.4. > Python prints the version on stdout since 3.4 -- before it used stderr: > 3.3$ ./python -V 2> /dev/null > 3.3$ ./python -V > /dev/null > Python 3.3.2+ > >

[issue18920] argparse module version action

Ezio Melotti added the comment: Only on 3.4. Python prints the version on stdout since 3.4 -- before it used stderr: 3.3$ ./python -V 2> /dev/null 3.3$ ./python -V > /dev/null Python 3.3.2+ 3.4$ ./python -V 2> /dev/null Python 3.4.0a1+ 3.4$ ./python -V > /dev/null This might also explain why ar

[issue18920] argparse module version action

Eli Bendersky added the comment: Yes, it seems like an oversight to me. Printing --version to stdout is more customary (Python itself does it, and most other tools do too). A question comes up about backwards compatibility. I would definitely not change it in 2.x - it's just not worth it. As f

[issue18920] argparse module version action

New submission from Wolfgang Maier: Hi, I just noticed that version output generated via the **'version' action** of the **argparse** module is routed to stderr. I'd expect regular output to go to stdout instead. The current behavior also seems inconsistent to me because --help prints to stdout.