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
Unable to copy 'C:\\Users\\<user>\\AppData\\Local\\Python\\pythoncore-3.12-64\\venvwlauncher.exe'
Unable to copy 'C:\\Users\\<user>\\AppData\\Local\\Python\\pythoncore-3.12-64\\venvlauncher.exe'
Error: [WinError 2] The system cannot find the file specified
Thank you for finding this! I can't believe it slipped through, I know I tested it at various times.
It looks like when free-threading support was added, the venv scripts were no longer renamed from venvlauncher to python during build, but for repackaging older versions the new script was used.
I'll need to repackage those releases, which is a bit annoying, but unavoidable it seems. In the meantime, this Powershell command will fix up any installs:
Oh, and in case anyone notices that the error message refers to the prefix directory instead of Lib\venv\scripts\nt, it's because the first failure is swallowed and the second attempt (assuming it's a source tree) is reported. Once we find the file in the right place, the case that's being reported isn't even checked.
Thanks for the report. I'm going through and republishing the 3.11 and 3.12 packages right now, so an alternative fix will (soon) be to py install 3.12 --force to replace your existing install. The Powershell command above will be faster, though.
Activity
zooba commentedon Jun 13, 2025
Thank you for finding this! I can't believe it slipped through, I know I tested it at various times.
It looks like when free-threading support was added, the venv scripts were no longer renamed from
venvlaunchertopythonduring build, but for repackaging older versions the new script was used.I'll need to repackage those releases, which is a bit annoying, but unavoidable it seems. In the meantime, this Powershell command will fix up any installs:
zooba commentedon Jun 13, 2025
Oh, and in case anyone notices that the error message refers to the prefix directory instead of
Lib\venv\scripts\nt, it's because the first failure is swallowed and the second attempt (assuming it's a source tree) is reported. Once we find the file in the right place, the case that's being reported isn't even checked.zooba commentedon Jun 13, 2025
Thanks for the report. I'm going through and republishing the 3.11 and 3.12 packages right now, so an alternative fix will (soon) be to
py install 3.12 --forceto replace your existing install. The Powershell command above will be faster, though.