Author christian.heimes
Recipients BreamoreBoy, alanjds, amaury.forgeotdarc, amiseler, christian.heimes, jcea, mhammond, pysquared, santoso.wijaya, techtonik, tim.peters, tim_evans
Date 2013-06-26.11:11:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1372245101.11.0.51364068262.issue706263@psf.upfronthosting.co.za>
In-reply-to
Content
I recommend against changing the code so late in the Python 2.7 release cycle. A change in behavior is too confusing.
And it's not a bug but a design decision, too. Over five years ago I implement parts of the IO interaction with the operating system for Python 3.0. I deliberately did NOT port modifications to 2.6.

If you want to get Python 3.x style print() behavior in Python 2.7 you can have it already:

from __future__ import print_function
import sys
if sys.executable.endswith("pythonw.exe"):
    sys.stdout = sys.stdout = None

print("can handle sys.stdout = None just fine.")
History
Date User Action Args
2013-06-26 11:11:41christian.heimessetrecipients: + christian.heimes, tim.peters, mhammond, jcea, pysquared, amaury.forgeotdarc, amiseler, tim_evans, techtonik, alanjds, santoso.wijaya, BreamoreBoy
2013-06-26 11:11:41christian.heimessetmessageid: <1372245101.11.0.51364068262.issue706263@psf.upfronthosting.co.za>
2013-06-26 11:11:41christian.heimeslinkissue706263 messages
2013-06-26 11:11:40christian.heimescreate