![]() ## Summary Should fix #2092. This PR changes `uv venv` so it also creates symlinks to `pypy` on Unix and copies executables on Windows when creating a new environment using PyPy. I found a bit of discrepancy between creation of a venv using `python` and `uv`, as using `python` brings all the executables with it. While `uv` brings only those without any version number, at least on Windows. The behaviour is different on Unix as we take the versioned symlinks too. Some examples below. `python -m venv` generates the following `Scripts` folder. ``` Mode LastWriteTime Length Name ---- ------------- ------ ---- -a---- 7/14/2024 15:41 2031 activate -a---- 7/14/2024 15:41 1029 activate.bat -a---- 7/14/2024 15:41 9033 Activate.ps1 -a---- 7/14/2024 15:41 393 deactivate.bat -a---- 7/14/2024 15:40 27648 libffi-8.dll -a---- 7/14/2024 15:41 44290560 libpypy3.10-c.dll -a---- 7/14/2024 15:41 108424 pip.exe -a---- 7/14/2024 15:41 108424 pip3.10.exe -a---- 7/14/2024 15:41 108424 pip3.exe -a---- 7/14/2024 15:41 79360 pypy.exe -a---- 7/14/2024 15:41 79360 pypy3.10.exe -a---- 7/14/2024 15:41 79360 pypy3.10w.exe -a---- 7/14/2024 15:41 79360 pypy3.exe -a---- 7/14/2024 15:41 79360 pypyw.exe -a---- 7/14/2024 15:41 79360 python.exe -a---- 7/14/2024 15:41 79360 python3.10.exe -a---- 7/14/2024 15:41 79360 python3.exe -a---- 7/14/2024 15:41 79360 pythonw.exe ``` `uv venv` instead generates this. ``` -a---- 7/14/2024 16:27 3360 activate -a---- 7/14/2024 16:27 2251 activate.bat -a---- 7/14/2024 16:27 2627 activate.csh -a---- 7/14/2024 16:27 4191 activate.fish -a---- 7/14/2024 16:27 3875 activate.nu -a---- 7/14/2024 16:27 2766 activate.ps1 -a---- 7/14/2024 16:27 2378 activate_this.py -a---- 7/14/2024 16:27 1728 deactivate.bat -a---- 7/13/2024 19:19 27648 libffi-8.dll -a---- 7/13/2024 19:19 44290560 libpypy3.10-c.dll -a---- 7/14/2024 16:27 1215 pydoc.bat -a---- 7/13/2024 19:19 79360 pypy.exe -a---- 7/13/2024 19:19 79360 pypyw.exe -a---- 7/13/2024 19:19 79360 python.exe -a---- 7/13/2024 19:19 79360 pythonw.exe ``` ## Test Plan To verify the correct behaviour: 1. Download and install PyPy from [official website](https://www.pypy.org/download.html) 2. Call `uv venv -p <path_to_pypy_>` 3. Run `.\.venv\Scripts\activate` on Windows or `./.venv/Scripts/activate` on Unix 4. Run `pypy` I thought of writing some automated tests but I couldn't rely on `uv python install` command to install PyPy as it's not in the list of installable Python builds. |
||
---|---|---|
.. | ||
bench | ||
cache-key | ||
distribution-filename | ||
distribution-types | ||
install-wheel-rs | ||
once-map | ||
pep440-rs | ||
pep508-rs | ||
platform-tags | ||
pypi-types | ||
requirements-txt | ||
uv | ||
uv-auth | ||
uv-build | ||
uv-cache | ||
uv-cli | ||
uv-client | ||
uv-configuration | ||
uv-dev | ||
uv-dispatch | ||
uv-distribution | ||
uv-extract | ||
uv-fs | ||
uv-git | ||
uv-installer | ||
uv-macros | ||
uv-normalize | ||
uv-python | ||
uv-requirements | ||
uv-resolver | ||
uv-scripts | ||
uv-settings | ||
uv-shell | ||
uv-state | ||
uv-tool | ||
uv-trampoline | ||
uv-types | ||
uv-version | ||
uv-virtualenv | ||
uv-warnings | ||
README.md |
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.
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-types
.
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-python
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-requirements
Utilities for reading package requirements from pyproject.toml
and requirements.txt
files.
uv-resolver
Functionality for resolving Python packages and their dependencies.
uv-shell
Utilities for detecting and manipulating shell environments.
uv-types
Shared traits for uv, to avoid circular dependencies.
pypi-types
General-purpose type definitions for types used in PyPI-compatible APIs.
uv-virtualenv
A venv
replacement to create virtual environments in Rust.
uv-warnings
User-facing warnings for uv.
requirements-txt
Functionality for parsing requirements.txt
files.