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 amaury.forgeotdarc
Recipients amaury.forgeotdarc, techtonik
Date 2013-06-25.10:26:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
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:15amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, techtonik
2013-06-25 10:26:15amaury.forgeotdarcsetmessageid: <>
2013-06-25 10:26:15amaury.forgeotdarclinkissue18298 messages
2013-06-25 10:26:15amaury.forgeotdarccreate