This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Alexey Muranov
Recipients Alexey Muranov
Date 2016-03-26.12:05:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1458993901.75.0.219308453251.issue26645@psf.upfronthosting.co.za>
In-reply-to
Content
I believe that printing help and usage messages to stdout is a design error.

In stdout i expect to find the output of my program, not help or diagnostic messages.  It is strange to see nothing printed on the screen (where stderr usually goes), and then to find help, usage, or *error* messages in the file where stdout was sent.  (Yes, argparse prints even error messages to stdout by default).

This issue has been discussed before because the implementation did not agree with the documentation: http://bugs.python.org/issue10728
I believe that the conclusion to adjust the documentation to the implementation was a mistake.

P.S. Compare with the direction of the output of `grep -h` or `git -h`.
History
Date User Action Args
2016-03-26 12:05:01Alexey Muranovsetrecipients: + Alexey Muranov
2016-03-26 12:05:01Alexey Muranovsetmessageid: <1458993901.75.0.219308453251.issue26645@psf.upfronthosting.co.za>
2016-03-26 12:05:01Alexey Muranovlinkissue26645 messages
2016-03-26 12:05:01Alexey Muranovcreate