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 hokiedsp
Recipients hokiedsp, paul.moore, steve.dower, tim.golden, zach.ware
Date 2022-02-08.22:48:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
After months of proper operation, my per-user Python install started to error out when I attempt `python -m venv .venv` with 

"Error: Command '['C:\\Users\\kesh\\test\\.venv\\Scripts\\python.exe', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 101."

Following the StackOverflow solution, I reinstalled Python for all users and it was working OK. I recently looked into it deeper and found the root issue in the function PC/launcher.c/run_child(). The path to the "...\Python\Python310\python.exe" contains a space, and the CreateProcessW() call on Line 811 is passing the path without quoting the path, causing the process creation to fail.

I fixed my issue by using the Windows short path convention on my path env. variable, but there must be a more permanent fix possible.

Here is the link to my question and self-answering to the problem:
Date User Action Args
2022-02-08 22:48:39hokiedspsetrecipients: + hokiedsp, paul.moore, tim.golden, zach.ware, steve.dower
2022-02-08 22:48:39hokiedspsetmessageid: <>
2022-02-08 22:48:39hokiedsplinkissue46686 messages
2022-02-08 22:48:39hokiedspcreate