[issue46686] [venv / PC/launcher] issue with a space in the installed python path

[Kesh Ikuma]

Kesh Ikuma  added the comment:

> a file named "C:\Program". Now the venv launcher won't be able to execute

This is exactly what happened on my PC, and the behavior was triggered by 
Microsoft Visual C++ 2015-2022 Redistributable installer. The installer left a 
log file "C:\Users\Kesh" with my account "C:\Users\Kesh Ikuma".

Thank you for quickly addressing the issue

--

___
Python tracker 
<https://bugs.python.org/issue46686>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue46686] [venv / PC/launcher] issue with a space in the installed python path

[Kesh Ikuma]

Kesh Ikuma  added the comment:

@eryksun - I knew the reproducibility is the issue with this bug. On the same 
PC I've been having a problem with, I created another dummy account with a 
space in its username, and it worked flawlessly... So, it's something I've done 
to my account which triggered this behavior. 

Is there anything that I can try and report on my machine? I'd be happy to do so

--

___
Python tracker 
<https://bugs.python.org/issue46686>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue46686] [venv / PC/launcher] issue with a space in the installed python path

[Kesh Ikuma]

New submission from Kesh Ikuma :

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:

https://stackoverflow.com/questions/71039131/troubleshooting-the-windows-venv-error-101

--
components: Windows
messages: 412874
nosy: hokiedsp, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: [venv / PC/launcher] issue with a space in the installed python path
type: behavior
versions: Python 3.10, Python 3.8, Python 3.9

___
Python tracker 
<https://bugs.python.org/issue46686>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com