[issue9713] Py_CompileString fails on non decode-able paths.

STINNER Victor added the comment: See issue #10114: fixed in Python 3.1 (r85716) and in Python 3.2 (r85569+r85570). -- resolution: -> fixed status: open -> closed ___ Python tracker __

[issue9713] Py_CompileString fails on non decode-able paths.

STINNER Victor added the comment: See also issue #10114. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue9713] Py_CompileString fails on non decode-able paths.

STINNER Victor added the comment: #6543 changed the encoding of the filename argument of PyRun_SimpleFileExFlags() (and all functions based on PyRun_SimpleFileExFlags) and c_filename attribute of the compiler (private) structure in Python 3.1.3: use utf-8 in strict mode instead of filesystem

[issue9713] Py_CompileString fails on non decode-able paths.

Changes by STINNER Victor : -- components: +Unicode -None versions: +Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue9713] Py_CompileString fails on non decode-able paths.

STINNER Victor added the comment: The problem is not specific to Py_CompileString(): all functions based (indirectly) on PyParser_ASTFromString() and PyParser_ASTFromFile() expect filenames encoded in utf-8 with the strict error handler. If we choose to use something else than utf-8 in strict

[issue9713] Py_CompileString fails on non decode-able paths.

Changes by Éric Araujo : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/

[issue9713] Py_CompileString fails on non decode-able paths.

New submission from Campbell Barton : On linux I have a path which python reads as... /data/test/num\udce9ro_bad/untitled.blend os.listdir("/data/test/") returns this ['num\udce9ro_bad'] But the same path cant be given to the C api's Py_CompileString Where fn is '/data/test/num\udce9ro_bad/un