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

PEP 514 support #1521

Closed
zanieb opened this issue Feb 16, 2024 · 2 comments · Fixed by #6761
Closed

PEP 514 support #1521

zanieb opened this issue Feb 16, 2024 · 2 comments · Fixed by #6761
Labels
help wanted Contribution especially encouraged windows Specific to the Windows platform

Comments

@zanieb
Copy link
Member

zanieb commented Feb 16, 2024

https://peps.python.org/pep-0514/

We use py to find Python installations on Windows today but we want to switch to registry look-ups per PEP 514

@zanieb zanieb added the windows Specific to the Windows platform label Feb 16, 2024
@gaborbernat
Copy link
Contributor

@gaborbernat
Copy link
Contributor

tox-uv seems to be failing on Github Actions without this https://github.com/tox-dev/tox-uv/actions/runs/7935511069?pr=2

zanieb added a commit that referenced this issue Feb 18, 2024
Similar idea to #1356 

Attempting to reproduce
#1521 (comment)
@zanieb zanieb added the help wanted Contribution especially encouraged label Aug 22, 2024
konstin added a commit that referenced this issue Aug 28, 2024
Our current strategy of parsing the output of `py --list-paths` to get the installed python versions on windows is brittle (#6524, missing `py`, etc.) and it's slow (10ms last time i measured).

Instead, we should behave spec-compliant and read the python versions from the registry following PEP 514.

We're using the official rust-for-windows crates for accessing the registry.

Fixes #1521
Fixes #6524
konstin added a commit that referenced this issue Aug 28, 2024
Our current strategy of parsing the output of `py --list-paths` to get the installed python versions on windows is brittle (#6524, missing `py`, etc.) and it's slow (10ms last time i measured).

Instead, we should behave spec-compliant and read the python versions from the registry following PEP 514.

We're using the official rust-for-windows crates for accessing the registry.

Fixes #1521
Fixes #6524
konstin added a commit that referenced this issue Aug 28, 2024
Our current strategy of parsing the output of `py --list-paths` to get the installed python versions on windows is brittle (#6524, missing `py`, etc.) and it's slow (10ms last time i measured).

Instead, we should behave spec-compliant and read the python versions from the registry following PEP 514.

We're using the official rust-for-windows crates for accessing the registry.

Fixes #1521
Fixes #6524
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Contribution especially encouraged windows Specific to the Windows platform
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants