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 Sworddragon
Recipients Sworddragon, a.badger, bkabrda, larry, lemburg, loewis, ncoghlan, pitrou, r.david.murray, serhiy.storchaka, terry.reedy, vstinner
Date 2013-12-09.13:48:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> If the environment variable is not enough

There is a big difference between environment variables and internal calls: Environment variables are user-space while builtin/library functions are developer-space.

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

Thanks for the clarification. I wished somebody had sayed me that after this sentence in my startpost: "It seems that print() and write() (and maybe other of such I/O functions) are relying on sys.getfilesystemencoding()."

In theory this makes already my ticket invalid. Well, but now I would wish print() would allow to choose the encoding like open() too^^
Date User Action Args
2013-12-09 13:48:16Sworddragonsetrecipients: + Sworddragon, lemburg, loewis, terry.reedy, ncoghlan, pitrou, vstinner, larry, a.badger, r.david.murray, serhiy.storchaka, bkabrda
2013-12-09 13:48:16Sworddragonsetmessageid: <>
2013-12-09 13:48:16Sworddragonlinkissue19846 messages
2013-12-09 13:48:15Sworddragoncreate