Message124273
I think this is a documentation bug, since IMO help should print on stdout, not stderr[1]. I would expect print_usage to do likewise, but for the error to tell print_usage to write to stderr when it calls it...which is exactly what the code does.
[1] I know some unix commands print help to stderr, and this really annoys me when I pipe long help output to less....and it *still* scrolls off the screen. |
|
Date |
User |
Action |
Args |
2010-12-18 04:09:27 | r.david.murray | set | recipients:
+ r.david.murray, bethard, docs@python, silvioricardoc |
2010-12-18 04:09:27 | r.david.murray | set | messageid: <1292645367.34.0.807495842474.issue10728@psf.upfronthosting.co.za> |
2010-12-18 04:09:25 | r.david.murray | link | issue10728 messages |
2010-12-18 04:09:25 | r.david.murray | create | |
|