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 larry
Recipients Sworddragon, a.badger, bkabrda, larry, lemburg, loewis, ncoghlan, pitrou, r.david.murray, serhiy.storchaka, terry.reedy, vstinner
Date 2013-12-09.13:28:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> The fact that write() uses sys.getfilesystemencoding() is either
> a defect or a bad design (I leave the decision to you).

I have good news for you.  write() does not cal sys.getfilesystemencoding(), because the encoding is set at the time the file is opened.

> But I'm still missing a reply to my suggestion. As I'm seeing it
> has no disadvantages to give the developer optionally the control.

The programmer has all the control they need.  They can open their own pipes using any encoding they like, and they can even reopen stdin/stdout with a different encoding if they wish.
Date User Action Args
2013-12-09 13:28:57larrysetrecipients: + larry, lemburg, loewis, terry.reedy, ncoghlan, pitrou, vstinner, a.badger, r.david.murray, Sworddragon, serhiy.storchaka, bkabrda
2013-12-09 13:28:57larrysetmessageid: <>
2013-12-09 13:28:57larrylinkissue19846 messages
2013-12-09 13:28:57larrycreate