[issue26645] argparse prints help messages to stdout instead of stderr by default

Alexey Muranov added the comment: My grep man page says --help Print a brief help message. but indeed there is no `--help` in usage message. Maybe this is a bug of the man page. Thanks for the explanation. -- ___ Python tracker

[issue26645] argparse prints help messages to stdout instead of stderr by default

Serhiy Storchaka added the comment: Does FreeBSD grep support the `--help` option? Long options is GNU extension, classical UNIX commands supported only short options. -- ___ Python tracker ___

[issue26645] argparse prints help messages to stdout instead of stderr by default

Alexey Muranov added the comment: Thanks for the explanation, this makes sense. I did not notice that argparse outputs to stderr if command line arguments are wrong, i was probably wrong when said it prints error messages to stdout. I did not notice indeed that there were no `-h` option in g

[issue26645] argparse prints help messages to stdout instead of stderr by default

Serhiy Storchaka added the comment: `grep --help` outputs to stdout. `grep -h` outputs to stderr, because this is error, there is no the `-h` flag. The same for git and most other command line tools. argparse follows this behavior. There is no bug. -- nosy: +serhiy.storchaka resolutio

[issue26645] argparse prints help messages to stdout instead of stderr by default

Changes by SilentGhost : -- nosy: +bethard versions: +Python 3.6 -Python 3.5 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue26645] argparse prints help messages to stdout instead of stderr by default

New submission from Alexey Muranov: 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 fi