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 Suzumizaki
Recipients Suzumizaki, dstufft, eric.araujo
Date 2019-07-12.02:28:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
`distutils.util.byte_compile` fails _indirect_ byte compiling when the
full-path of the .py file contains non-ASCII characters.

Because there is the project (cx_Freeze) which directly uses
`distutils.util.byte_compile`, the problem would happen while installing it
under the non-ASCII path.

Fortunately, it is easy to fix.
Ofcourse, the files included in external libraries should be named ASCII only,
but `distutils.util.byte_compile` makes and uses full path of them. I learned
many of libraries uses setuptools instead of distutils, but please consider
the following situations:

1) The case that venv creates the virtual environment under or with
   non-ASCII named folder.
2) And special cases of 1), on Windows, the name of end-users OFTEN be
   composed with non-ASCII characters, this means including theirs
   Documents, Desktop, or Downloads etc.

The more they are not professional,they make easily the situation above.
Date User Action Args
2019-07-12 02:28:51Suzumizakisetrecipients: + Suzumizaki, eric.araujo, dstufft
2019-07-12 02:28:51Suzumizakisetmessageid: <>
2019-07-12 02:28:50Suzumizakilinkissue37570 messages
2019-07-12 02:28:50Suzumizakicreate