[issue1552880] [Python2] Use utf-8 in the import machinery on Windows to support unicode paths

STINNER Victor added the comment: FYI, I finished my work on non-ascii filenames in Python 3.2 (#8611, #9425): Python 3.2 now suports any filename with any locale (filesystem) encoding. -- ___ Python tracker __

[issue1552880] [Python2] Use utf-8 in the import machinery on Windows to support unicode paths

Martin v. Löwis added the comment: Having patches in the tracker is fine to me. Even if the patch is closed, it's still available. Of course, there are many ways to publish code on the net: you could post the patch to Rietveld, to the Python wiki, or publish an entire clone to bitbucket. ---

[issue1552880] [Python2] Use utf-8 in the import machinery on Windows to support unicode paths

Éric Araujo added the comment: There is no such place that I know of, sorry. -- stage: -> committed/rejected ___ Python tracker ___ __

[issue1552880] [Python2] Use utf-8 in the import machinery on Windows to support unicode paths

Kristján Valur Jónsson added the comment: Well, it was, originally, but it met with so little interest that I couldn't be bothered to polish it to inclusion standards. Anyway, there was the incompatibility problem of what to do with the __file__ attribute, and the fact that the patch was Win

[issue1552880] [Python2] Use utf-8 in the import machinery on Windows to support unicode paths

Martin v. Löwis added the comment: As this was never meant for inclusion in Python, and apparently confuses people, I'm closing it - it couldn't go into 2.x, anyway. -- resolution: -> out of date status: open -> closed ___ Python tracker

[issue1552880] [Python2] Use utf-8 in the import machinery on Windows to support unicode paths

STINNER Victor added the comment: Oh, I didn't see that the issue was specific to Python2. I updated the issue's title. If I understood correctly, the issue is also specific to Windows. Do you know if your patch changes the public API? (break the compatibility) -- FYI about Python3: > That'