You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To support free-threaded builds, the Windows venv redirector executables have been renamed in Python 3.13.
The executables were under Lib/venv/scripts/nt and were named python.exe and pythonw.exe. They have been renamed to venvlauncher.exe and venvwlauncher.exe respectively. This causes virtualenv not to find the shim and to copy DLLs, etc., into the virtual environment.
There may be other issues because of this change.
In the meantime, a possible workaround could be to create file symbolic links.
To support free-threaded builds, the Windows venv redirector executables have been renamed in Python 3.13.
The executables were under
Lib/venv/scripts/nt
and were namedpython.exe
andpythonw.exe
. They have been renamed tovenvlauncher.exe
andvenvwlauncher.exe
respectively. This causes virtualenv not to find the shim and to copy DLLs, etc., into the virtual environment.There may be other issues because of this change.
In the meantime, a possible workaround could be to create file symbolic links.
References:
The text was updated successfully, but these errors were encountered: