b983ff4fa7
`uv --system` is failing in GitHub Actions, because `py --list-paths` returns all the pre-cached Pythons: ``` -V:3.12 * C:\hostedtoolcache\windows\Python\3.12.2\x64\python.exe -V:3.12-32 C:\hostedtoolcache\windows\Python\3.12.2\x86\python.exe -V:3.11 C:\hostedtoolcache\windows\Python\3.11.8\x64\python.exe -V:3.11-32 C:\hostedtoolcache\windows\Python\3.11.8\x86\python.exe -V:3.10 C:\hostedtoolcache\windows\Python\3.10.11\x64\python.exe -V:3.10-32 C:\hostedtoolcache\windows\Python\3.10.11\x86\python.exe -V:3.9 C:\hostedtoolcache\windows\Python\3.9.13\x64\python.exe -V:3.9-32 C:\hostedtoolcache\windows\Python\3.9.13\x86\python.exe -V:3.8 C:\hostedtoolcache\windows\Python\3.8.10\x64\python.exe -V:3.8-32 C:\hostedtoolcache\windows\Python\3.8.10\x86\python.exe -V:3.7 C:\hostedtoolcache\windows\Python\3.7.9\x64\python.exe -V:3.7-32 C:\hostedtoolcache\windows\Python\3.7.9\x86\python.exe ``` So, our default selector returns the first entry here. But none of these are actually in `PATH` except the one that the user installed via `actions/setup-python@v5` -- that's the point of the action, that it puts the correct versions in `PATH`. It seems to me like we should prioritize `PATH` over `py --list-paths`. Is there a good reason not to do this? Closes: https://github.com/astral-sh/uv/issues/2056
Crates
bench
Functionality for benchmarking uv.
cache-key
Generic functionality for caching paths, URLs, and other resources across platforms.
distribution-filename
Parse built distribution (wheel) and source distribution (sdist) filenames to extract structured metadata.
distribution-types
Abstractions for representing built distributions (wheels) and source distributions (sdists), and the sources from which they can be downloaded.
gourgeist
A venv replacement to create virtual environments in Rust.
install-wheel-rs
Install built distributions (wheels) into a virtual environment.]
once-map
A waitmap-like concurrent hash map for executing tasks
exactly once.
pep440-rs
Utilities for interacting with Python version numbers and specifiers.
pep508-rs
Utilities for interacting with PEP 508 dependency specifiers.
platform-host
Functionality for detecting the current platform (operating system, architecture, etc.).
platform-tags
Functionality for parsing and inferring Python platform tags as per PEP 425.
uv
Command-line interface for the uv package manager.
uv-build
A PEP 517-compatible build frontend for uv.
uv-cache
Functionality for caching Python packages and associated metadata.
uv-client
Client for interacting with PyPI-compatible HTTP APIs.
uv-dev
Development utilities for uv.
uv-dispatch
A centralized struct for resolving and building source distributions in isolated environments.
Implements the traits defined in uv-traits.
uv-distribution
Client for interacting with built distributions (wheels) and source distributions (sdists). Capable of fetching metadata, distribution contents, etc.
uv-extract
Utilities for extracting files from archives.
uv-fs
Utilities for interacting with the filesystem.
uv-git
Functionality for interacting with Git repositories.
uv-installer
Functionality for installing Python packages into a virtual environment.
uv-interpreter
Functionality for detecting and leveraging the current Python interpreter.
uv-normalize
Normalize package and extra names as per Python specifications.
uv-package
Types and functionality for working with Python packages, e.g., parsing wheel files.
uv-resolver
Functionality for resolving Python packages and their dependencies.
uv-traits
Shared traits for uv, to avoid circular dependencies.
pypi-types
General-purpose type definitions for types used in PyPI-compatible APIs.
uv-warnings
User-facing warnings for uv.
requirements-txt
Functionality for parsing requirements.txt files.