Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run Windows against Python 3.13 #2171

Merged
merged 3 commits into from
Mar 4, 2024
Merged

Run Windows against Python 3.13 #2171

merged 3 commits into from
Mar 4, 2024

Conversation

charliermarsh
Copy link
Member

@charliermarsh charliermarsh commented Mar 4, 2024

Summary

In Python 3.13, at least in the current builds, there's no python.exe, but there is venvlauncher.exe.

I've asked here about whether it's intended: https://discuss.python.org/t/when-should-venv-scripts-nt-python-exe-be-present/47620. But there's at least some evidence in CPython here that we should fall back to these, and the tests pass.

Closes #1636.

@charliermarsh charliermarsh force-pushed the charlie/win branch 3 times, most recently from 77eae53 to 477ef70 Compare March 4, 2024 21:35
@charliermarsh charliermarsh added bug Something isn't working windows Specific to the Windows platform labels Mar 4, 2024
@charliermarsh charliermarsh marked this pull request as ready for review March 4, 2024 21:45
@charliermarsh charliermarsh enabled auto-merge (squash) March 4, 2024 21:45
@charliermarsh charliermarsh merged commit 70143b8 into main Mar 4, 2024
7 checks passed
@charliermarsh charliermarsh deleted the charlie/win branch March 4, 2024 21:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working windows Specific to the Windows platform
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Windows: "uv venv" gives "exit 2" with tox-uv
1 participant