Message191842
Yes, in pythonw.exe the C stderr is not really usable, and this leads to unpredictable results.
It's difficult to fix in python2 though; python3 has fixed this issue, but in a way that cannot be backported.
Some workarounds:
- don't use pythonw.exe in a console, it's meant to be a *windows* application, without standard streams. I'm actually surprised of the behavior of your first example.
- use python3, where pythonw will set sys.stderr to None, and prints will be silently discarded. |
|
Date |
User |
Action |
Args |
2013-06-25 10:26:15 | amaury.forgeotdarc | set | recipients:
+ amaury.forgeotdarc, techtonik |
2013-06-25 10:26:15 | amaury.forgeotdarc | set | messageid: <1372155975.91.0.953461757081.issue18298@psf.upfronthosting.co.za> |
2013-06-25 10:26:15 | amaury.forgeotdarc | link | issue18298 messages |
2013-06-25 10:26:15 | amaury.forgeotdarc | create | |
|