When typing py, I get the standard python version as set by %PY_PYTHON%, i.c. 3.10, even when a virtual environment (venv) is active.
When typing python, I get the python version from the venv, i.c. 3.11.
I expected the Python Launcher for Windows (py.exe) to prefer the CLI command argument py -<n.n> (if any) over venv over %PY_PYTHON%.
That was the way I recall py worked in 3.10. 3.11.0a7 had an issue in ignoring %PY_PYTHON%, which is now remedied in 3.11.0.b1 (thanks @zooba !). The venv part still seems to have an issue in 3.11.0b1.
(unsuccessfully looked for a way to add tags like Windows and 3.11 and 'nosy' people, like we did on the previous tracker, so hope this gets added in the process)
Could well be a regression. I'll have to look at the code, but it's probably picking up the environment variable as a preference rather than a default/fallback.
When typing
py
, I get the standard python version as set by%PY_PYTHON%
, i.c. 3.10, even when a virtual environment (venv
) is active.When typing
python
, I get the python version from thevenv
, i.c. 3.11.I expected the Python Launcher for Windows (
py.exe
) to prefer the CLI command argumentpy -<n.n>
(if any) overvenv
over%PY_PYTHON%
.That was the way I recall
py
worked in 3.10. 3.11.0a7 had an issue in ignoring%PY_PYTHON%
, which is now remedied in 3.11.0.b1 (thanks @zooba !). Thevenv
part still seems to have an issue in 3.11.0b1.Environment
Issue
The text was updated successfully, but these errors were encountered: