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 minghua
Recipients eryksun, ezio.melotti, minghua, paul.moore, serhiy.storchaka, steve.dower, tim.golden, vstinner, zach.ware
Date 2021-09-21.06:30:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1632205842.37.0.990838785358.issue45176@roundup.psfhosted.org>
In-reply-to
Content
Steve Dower (steve.dower) posted:
> I'd guess that these tests are assuming that sys.executable contains only ASCII characters. All the tests run in a non-ASCII working directory, so it's only the runtime that is not tested propersy here.
> 
> The easiest way for Ming Hua to test this is to install for all users (into Program Files), and run tests with the same user account.

I've already installed for all users, just not into the default "C:\Program Files\", but instead "C:\Programs\Python\".  I don't think it's the executable's path that is problematic, but the temporary directory where the tests are run (%LOCALAPPDATA%\Temp\tmpcwkfn9ct, where %LOCALAPPDATA% is C:\Users\<account name>\AppData\Local and therefore contains non-ASCII characters).

Both of these paths are shown in the error/failure logs posted in the first message.

I doubt installing into "C:\Program Files\" would make a difference.
History
Date User Action Args
2021-09-21 06:30:42minghuasetrecipients: + minghua, paul.moore, vstinner, tim.golden, ezio.melotti, zach.ware, serhiy.storchaka, eryksun, steve.dower
2021-09-21 06:30:42minghuasetmessageid: <1632205842.37.0.990838785358.issue45176@roundup.psfhosted.org>
2021-09-21 06:30:42minghualinkissue45176 messages
2021-09-21 06:30:42minghuacreate