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 paul.moore
Recipients eryksun, jan, paul.moore, steve.dower, tim.golden, zach.ware
Date 2017-03-15.14:32:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1489588345.08.0.725284839897.issue29817@psf.upfronthosting.co.za>
In-reply-to
Content
Also, this is a Python 2 only issue. The problem doesn't happen in Python 3.6 (at least in my quick experiment). I'm not 100% sure if this is because the internal implementation of IO changed in 3.x, or if it's just because we're now using a newer CRT which has fixed the issue.

I agree that there's no point in Python trying to work around this behaviour.
History
Date User Action Args
2017-03-15 14:32:25paul.mooresetrecipients: + paul.moore, tim.golden, zach.ware, eryksun, steve.dower, jan
2017-03-15 14:32:25paul.mooresetmessageid: <1489588345.08.0.725284839897.issue29817@psf.upfronthosting.co.za>
2017-03-15 14:32:25paul.moorelinkissue29817 messages
2017-03-15 14:32:25paul.moorecreate