Bug report
Bug description:
Intel/Win11, latest updates
C:\Users\Z B\AppData\Local\Python\pythoncore-3.14.64\python.exe -m venv --system-site-packages D:\ProjectA
which worked with 3.14.0, now creates a venv "--system-site-packages" in the current working directory with include-system-site-packages = false in pyvenv.cfg, and a 2nd venv under D:\ProjectA, also with include-system-site-packages = false. This is repeatable. Clean removal and reinstall of python, fresh empty project directory.
Initially thinking it was user error, I tried a number of things without taking notes: in ONE instance, I recall observing that one of the paths (home, executable, or command) in the pyvenv.cfg file was simply "C:\Z" - meaning that it broke at the space between Z and B - not word wrap, that was the entire path. I have been unable to repeat this effect. However, the other two paths were full and correct. So this leads the hypothesis that Windows userids that have spaces may now be an issue. I tried using the fully qualified path enclosed in quotes for the executable on the command line, and obtain the result described above.
I used the same scripts to create venvs with 3.13 without this issue occurring.
CPython versions tested on:
3.14, 3.13
Operating systems tested on:
Windows
Bug report
Bug description:
Intel/Win11, latest updates
C:\Users\Z B\AppData\Local\Python\pythoncore-3.14.64\python.exe -m venv --system-site-packages D:\ProjectA
which worked with 3.14.0, now creates a venv "--system-site-packages" in the current working directory with include-system-site-packages = false in pyvenv.cfg, and a 2nd venv under D:\ProjectA, also with include-system-site-packages = false. This is repeatable. Clean removal and reinstall of python, fresh empty project directory.
Initially thinking it was user error, I tried a number of things without taking notes: in ONE instance, I recall observing that one of the paths (home, executable, or command) in the pyvenv.cfg file was simply "C:\Z" - meaning that it broke at the space between Z and B - not word wrap, that was the entire path. I have been unable to repeat this effect. However, the other two paths were full and correct. So this leads the hypothesis that Windows userids that have spaces may now be an issue. I tried using the fully qualified path enclosed in quotes for the executable on the command line, and obtain the result described above.
I used the same scripts to create venvs with 3.13 without this issue occurring.
CPython versions tested on:
3.14, 3.13
Operating systems tested on:
Windows