Author eryksun
Recipients eryksun, ezio.melotti, paul.moore, steve.dower, tianjg, tim.golden, vstinner, zach.ware
Date 2017-12-20.07:35:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1513755355.67.0.213398074469.issue32381@psf.upfronthosting.co.za>
In-reply-to
Content
run_file encodes the file path via PyUnicode_EncodeFSDefault, which encodes as UTF-8 in Windows, starting with 3.6. PyRun_SimpleFileExFlags subsequently tries to open this encoded path via _Py_fopen, which calls fopen. The CRT expects an ANSI encoded path, so only the common ASCII subset will work. Non-ASCII paths will fail.

This could be addressed in _Py_fopen by decoding the path and calling _wfopen instead of fopen. 

Executing a .pyc also fails in 3.5 if the wide-character path can't be encoded as ANSI, but the 3.5 branch only accepts security fixes.
History
Date User Action Args
2017-12-20 07:35:55eryksunsetrecipients: + eryksun, paul.moore, vstinner, tim.golden, ezio.melotti, zach.ware, steve.dower, tianjg
2017-12-20 07:35:55eryksunsetmessageid: <1513755355.67.0.213398074469.issue32381@psf.upfronthosting.co.za>
2017-12-20 07:35:55eryksunlinkissue32381 messages
2017-12-20 07:35:55eryksuncreate