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
Normally it's worth mentioning, except we know this will be the same issue as #118773. It's fixed for the next release.
Until then, if you disable pip then it should install, and you can patch your own tempfile.py to remove the mode=0o700 argument from any mkdir calls. I understand that's enough to get pip to run.
Bug report
Bug description:
I tried the installer on two Win11 Pro systems (23H2, 24H2 beta), upgrade from a6 and fresh install. On both systems pip was broken afterwards.
Error message:
"no module named pip"
On the 24H2 system additionally the "scripts" folder got deleted while upgrading. The a6 installer works fine.
CPython versions tested on:
3.13
Operating systems tested on:
Windows
The text was updated successfully, but these errors were encountered: