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-13.11:01:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1386932491.59.0.654504019093.issue19846@psf.upfronthosting.co.za>
In-reply-to
Content
>> 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.

Now after some researching I see I wasn't wrong at all. I should've been sayed:

"The fact that write() -> open() relies on sys.getfilesystemencoding() (respectively locale.getpreferredencoding()) at default as encoding is either a defect or a bad design (I leave the decision to you)."

Or am I overlooking something?
History
Date User Action Args
2013-12-13 11:01:31Sworddragonsetrecipients: + Sworddragon, lemburg, loewis, terry.reedy, ncoghlan, pitrou, vstinner, larry, a.badger, r.david.murray, serhiy.storchaka, bkabrda
2013-12-13 11:01:31Sworddragonsetmessageid: <1386932491.59.0.654504019093.issue19846@psf.upfronthosting.co.za>
2013-12-13 11:01:31Sworddragonlinkissue19846 messages
2013-12-13 11:01:31Sworddragoncreate