[issue706263] print raises exception when no console available

Mark Lawrence added the comment: Is it really worth leaving this open? There's no consensus after ten years and it only impacts on Python 2.7. Mark Hammond made his view plain in msg15198, which is supported by the fact that a type has yet to be allocated. -- ___

[issue706263] print raises exception when no console available

Amaury Forgeot d'Arc added the comment: Python 3 is not affected: pythonw.exe sets sys.stderr to None, and print() silently discards the output in this case. -- ___ Python tracker ___

[issue706263] print raises exception when no console available

Jesús Cea Avión added the comment: Does this affects Python 3? -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue706263] print raises exception when no console available

Santoso Wijaya added the comment: This is indeed reproducible in Python 2.7. The following unittest will expose it. However, patching sys.std* to None will break `print` statements to raise AttributeError in pythonw.exe programs, though it won't mysteriously break only after printing 4 kbytes

[issue706263] print raises exception when no console available

Changes by Santoso Wijaya : -- components: +IO ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue706263] print raises exception when no console available

Changes by Santoso Wijaya : -- nosy: +santa4nt versions: +Python 2.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue706263] print raises exception when no console available

Mark Lawrence added the comment: Ah I was misreading things, I too can confirm that it is still a problem. -- ___ Python tracker ___ ___

[issue706263] print raises exception when no console available

Amaury Forgeot d'Arc added the comment: I use Windows XP. Note that nothing is displayed on screen. there is just a error.txt file in the current directory. -- ___ Python tracker

[issue706263] print raises exception when no console available

Mark Lawrence added the comment: @Amaury I tested with Windows Vista and the latest 2.6 and 2.7 maintainance releases, what did you use? -- ___ Python tracker ___

[issue706263] print raises exception when no console available

Amaury Forgeot d'Arc added the comment: No, nothing changed in this aspect since python 2.2. With 2.7, I get the same error.txt file containing the "Bad file descriptor" message. -- resolution: out of date -> status: closed -> open ___ Python track

[issue706263] print raises exception when no console available

Mark Lawrence added the comment: Works fine with pythonw on 2.6 and 2.7. -- nosy: +BreamoreBoy resolution: -> out of date status: open -> closed ___ Python tracker ___ ___

[issue706263] print raises exception when no console available

Alan Justino added the comment: FWIW: I don't know if it changes anything, but when deploying Django projects on some clients who uses Windows as server, I'm using this piece of code to workarround this issue: ## Fixes "IOError: [Errno 9] Bad file descriptor" when in pythonw.exe of Windows i

[issue706263] print raises exception when no console available

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Python 3.0 already discards the output in this case (see issue1415): it sets sys.stdout=None and silently ignores prints to the None file. I think this is the correct behavior, but I'm not sure this can be backported to 2.7, because of