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 ncoghlan
Recipients Arfrever, berker.peksag, elixir, ishimoto, jwilk, loewis, martin.panter, methane, mrabarnett, ncoghlan, nikratio, pitrou, rurpy2, serhiy.storchaka, vstinner
Date 2015-05-16.14:42:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1431787339.44.0.396201303317.issue15216@psf.upfronthosting.co.za>
In-reply-to
Content
Revisiting the idea Nikolaus raised last year regarding whether or not this could be done using a dedicated API in the sys module, I realised today that even if we decided to use a separate public API, *that API* would still need a defined way to modify the stream encoding and error handling in place.

Since we're going to need the object level in-place modification API regardless, a separate sys module API for modifying the standard streams in particular would then introduce additional complexity without providing a proportional benefit.
History
Date User Action Args
2015-05-16 14:42:19ncoghlansetrecipients: + ncoghlan, loewis, ishimoto, pitrou, vstinner, jwilk, mrabarnett, Arfrever, methane, nikratio, rurpy2, berker.peksag, martin.panter, serhiy.storchaka, elixir
2015-05-16 14:42:19ncoghlansetmessageid: <1431787339.44.0.396201303317.issue15216@psf.upfronthosting.co.za>
2015-05-16 14:42:19ncoghlanlinkissue15216 messages
2015-05-16 14:42:19ncoghlancreate