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 JGoutin
Recipients JGoutin, lemburg, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2017-01-13.17:02:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1484326925.99.0.619121642157.issue29241@psf.upfronthosting.co.za>
In-reply-to
Content
Personally, I call "sys._enablelegacywindowsfsencoding()" for only one reason :
Temporary fixing issues with some third party libraries which use C code for files I/O (With filename as "mbcs" encoded bytes internally).

Theses libraries generally call "filename.encode(sys.getfilesystemencoding())" or "os.fsencode(filename)" before sending filenames from Python to C code.

Actually, I didn't see any side effect for using this function. Maybe because I call it at start before anything else.

Using the environment variable is not easy in my case.


I can look if encoding caching in fsencode is efficient (On Windows). And eventually propose a code change for this.
History
Date User Action Args
2017-01-13 17:02:06JGoutinsetrecipients: + JGoutin, lemburg, paul.moore, vstinner, tim.golden, zach.ware, steve.dower
2017-01-13 17:02:05JGoutinsetmessageid: <1484326925.99.0.619121642157.issue29241@psf.upfronthosting.co.za>
2017-01-13 17:02:05JGoutinlinkissue29241 messages
2017-01-13 17:02:05JGoutincreate