[issue11619] On Windows, don't encode filenames in the import machinery

Roundup Robot added the comment: New changeset df2fdd42b375 by Victor Stinner in branch 'default': Close #11619: The parser and the import machinery do not encode Unicode http://hg.python.org/cpython/rev/df2fdd42b375 -- resolution: -> fixed status: open -> closed __

[issue11619] On Windows, don't encode filenames in the import machinery

Changes by STINNER Victor : Removed file: http://bugs.python.org/file31446/parser_unicode-2.patch ___ Python tracker ___ ___ Python-bugs-list

[issue11619] On Windows, don't encode filenames in the import machinery

Changes by STINNER Victor : Removed file: http://bugs.python.org/file21759/parser_unicode.patch ___ Python tracker ___ ___ Python-bugs-list ma

[issue11619] On Windows, don't encode filenames in the import machinery

STINNER Victor added the comment: > I updated parser_unicode.patch to the last Python version. The new patch has > just a minor nit: test_symtable does crash :-D Fixed in new patch: parser_unicode-3.patch -- Added file: http://bugs.python.org/file31472/parser_unicode-3.patch

[issue11619] On Windows, don't encode filenames in the import machinery

STINNER Victor added the comment: I reopen the issue because some users are now requesting this feature. I updated parser_unicode.patch to the last Python version. The new patch has just a minor nit: test_symtable does crash :-D I will investigate the crash later. -- resolution: wont

[issue11619] On Windows, don't encode filenames in the import machinery

Changes by Eric Snow : -- nosy: +eric.snow ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue11619] On Windows, don't encode filenames in the import machinery

Steven Velez added the comment: This may be a small use case, but a use case none-the less. In my situation, I am distributing a frozen python package and it runs under the users home directory. If the user's name has international characters, this will fail. I expect we will have similar p

[issue11619] On Windows, don't encode filenames in the import machinery

Drekin added the comment: Is there a chance this will be fixed at least in Python 4? -- nosy: +Drekin ___ Python tracker ___ ___ Pytho

[issue11619] On Windows, don't encode filenames in the import machinery

STINNER Victor added the comment: The patch is really huge for such a very rare use case, so I prefer to close the issue as wont fix. Common cases with non-ASCII names are already handled correctly in Python 3.3. -- resolution: -> wont fix status: open -> closed _

[issue11619] On Windows, don't encode filenames in the import machinery

Changes by STINNER Victor : Removed file: http://bugs.python.org/file21743/compile_filename.patch ___ Python tracker ___ ___ Python-bugs-list

[issue11619] On Windows, don't encode filenames in the import machinery

STINNER Victor added the comment: Another huge patch to support Unicode filenames: parser_unicode.patch Doc/c-api/exceptions.rst | 26 +++--- Include/ast.h|5 ++ Include/compile.h| 15 +++- Include/parsetok.h | 42 ++- Includ

[issue11619] On Windows, don't encode filenames in the import machinery

STINNER Victor added the comment: compile_filename.patch: - Add PyErr_ProgramTextObject() and PyErr_WarnExplicitObject() functions - Store the filename as Unicode in compile.c - Remove the filename from get_ref_type() fatal error (I never see such fatal error, and I hope that it does never h

[issue11619] On Windows, don't encode filenames in the import machinery

STINNER Victor added the comment: > c) parse_source_module() > => covered by the issue #10785. Issue #10785 didn't change parse_source_module(): it does still encode the filename. We need Unicode version of PyParser_ASTFromFile() and PyAST_Compile(): a new version of these functions acceptin

[issue11619] On Windows, don't encode filenames in the import machinery

Roundup Robot added the comment: New changeset e4e92d68ba3a by Victor Stinner in branch 'default': Close #11619: write_compiled_module() doesn't encode the filename http://hg.python.org/cpython/rev/e4e92d68ba3a -- resolution: -> fixed stage: -> committed/rejected status: open -> close

[issue11619] On Windows, don't encode filenames in the import machinery

Roundup Robot added the comment: New changeset 1b7f484bab6e by Victor Stinner in branch 'default': Issue #11619: _PyImport_LoadDynamicModule() doesn't encode the path to bytes http://hg.python.org/cpython/rev/1b7f484bab6e -- nosy: +python-dev ___ Pyt

[issue11619] On Windows, don't encode filenames in the import machinery

STINNER Victor added the comment: dynload_win.patch: Fix part (a), _PyImport_LoadDynamicModule(). -- keywords: +patch Added file: http://bugs.python.org/file21321/dynload_win.patch ___ Python tracker _

[issue11619] On Windows, don't encode filenames in the import machinery

STINNER Victor added the comment: open_exclusive() was created by: changeset: 14708:89b2aee43e0b branch: legacy-trunk user:Guido van Rossum date:Wed Sep 20 20:31:38 2000 + files: Python/import.c description: On Unix, use O_EXCL when creating the .pyc/.pyo files

[issue11619] On Windows, don't encode filenames in the import machinery

Changes by Terry J. Reedy : -- nosy: +terry.reedy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue11619] On Windows, don't encode filenames in the import machinery

New submission from STINNER Victor : With #3080, Python 3.3 does now manipulate module paths and names as Unicode in the import machinery. But in 3 remaining places, it does encode filenames (to the ANSI code page): a) _PyImport_LoadDynamicModule() It should pass directly the PyObject* (inst