Meta

• License: Apache Software License, MIT License (MIT OR Apache-2.0)
• Author: uv
• Tags uv , requirements , packaging
• Requires: Python >=3.8

Classifiers

• Development Status
  • 4 - Beta
• Environment
  • Console
• Intended Audience
  • Developers
• License
  • OSI Approved :: Apache Software License
  • OSI Approved :: MIT License
• Operating System
  • OS Independent
• Programming Language
  • Python
  • Python :: 3 :: Only
  • Python :: 3.8
  • Python :: 3.9
  • Python :: 3.10
  • Python :: 3.11
  • Python :: 3.12
• Topic
  • Software Development :: Libraries
  • Software Development :: Quality Assurance
  • Software Development :: Testing

uv

👁 uv
👁 image
👁 image
👁 image
👁 Actions status
👁 Discord

An extremely fast Python package installer and resolver, written in Rust. Designed as a drop-in replacement for common pip and pip-tools workflows.

👁 Shows a bar chart with benchmark results.

Installing the Trio dependencies with a warm cache.

Highlights

• ⚖️ Drop-in replacement for common pip, pip-tools, and virtualenv commands.
• ⚡️ 10-100x faster than pip and pip-tools (pip-compile and pip-sync).
• 💾 Disk-space efficient, with a global cache for dependency deduplication.
• 🐍 Installable via curl, pip, pipx, etc. uv is a static binary that can be installed without Rust or Python.
• 🧪 Tested at-scale against the top 10,000 PyPI packages.
• 🖥️ Support for macOS, Linux, and Windows.
• 🧰 Advanced features such as dependency version overrides and alternative resolution strategies.
• ⁉️ Best-in-class error messages with a conflict-tracking resolver.
• 🤝 Support for a wide range of advanced pip features, including editable installs, Git dependencies, direct URL dependencies, local dependencies, constraints, source distributions, HTML and JSON indexes, and more.

uv is backed by Astral, the creators of Ruff.

Getting Started

Install uv with our standalone installers, or from PyPI:

# On macOS and Linux.
curl-LsSfhttps://astral.sh/uv/install.sh|sh

# On Windows.
powershell-c"irm https://astral.sh/uv/install.ps1 | iex"

# For a specific version.
curl-LsSfhttps://astral.sh/uv/0.2.15/install.sh|sh
powershell-c"irm https://astral.sh/uv/0.2.15/install.ps1 | iex"

# With pip.
pipinstalluv

# With pipx.
pipxinstalluv

# With Homebrew.
brewinstalluv

To create a virtual environment:

uvvenv# Create a virtual environment at .venv.

To activate the virtual environment:

# On macOS and Linux.
source.venv/bin/activate

# On Windows.
.venv\Scripts\activate

To install a package into the virtual environment:

uvpipinstallflask# Install Flask.
uvpipinstall-rrequirements.txt# Install from a requirements.txt file.
uvpipinstall-e.# Install the current project in editable mode.
uvpipinstall"package @ ."# Install the current project from disk.
uvpipinstall"flask[dotenv]"# Install Flask with "dotenv" extra.

To generate a set of locked dependencies:

uvpipcompilerequirements.in-orequirements.txt# Read a requirements.in file.
uvpipcompilepyproject.toml-orequirements.txt# Read a pyproject.toml file.
uvpipcompilesetup.py-orequirements.txt# Read a setup.py file.
echoflask|uvpipcompile--orequirements.txt# Read from stdin.
uvpipfreeze|uvpipcompile--orequirements.txt# Lock the current environment.

To sync a set of locked dependencies with the virtual environment:

uvpipsyncrequirements.txt# Install from a requirements.txt file.

uv's pip-install and pip-compile commands support many of the same command-line arguments as existing tools, including -r requirements.txt, -c constraints.txt, -e . (for editable installs), --index-url, and more.

Limitations

While uv supports a large subset of the pip interface, it does not support the entire feature set. In some cases, those differences are intentional; in others, they're a result of uv's early stage of development.

For details, see our pip compatibility guide.

Like pip-compile, uv generates a platform-specific requirements.txt file (unlike, e.g., poetry and pdm, which generate platform-agnostic poetry.lock and pdm.lock files). As such, uv's requirements.txt files may not be portable across platforms and Python versions.

Roadmap

uv is an extremely fast Python package resolver and installer, designed as a drop-in replacement for pip, pip-tools (pip-compile and pip-sync), and virtualenv.

uv represents an intermediary goal in our pursuit of a "Cargo for Python": a comprehensive project and package manager that is extremely fast, reliable, and easy to use.

Think: a single binary that bootstraps your Python installation and gives you everything you need to be productive with Python, bundling not only pip, pip-tools, and virtualenv, but also pipx, tox, poetry, pyenv, ruff, and more.

Our goal is to evolve uv into such a tool.

In the meantime, though, the narrower pip-tools scope allows us to solve the low-level problems involved in building such a tool (like package installation) while shipping something immediately useful with a minimal barrier to adoption.

Advanced Usage

Python discovery

uv itself does not depend on Python, but it does need to locate a Python environment to (1) install dependencies into the environment and (2) build source distributions.

When running pip sync or pip install, uv will search for a virtual environment in the following order:

• An activated virtual environment based on the VIRTUAL_ENV environment variable.
• An activated Conda environment based on the CONDA_PREFIX environment variable.
• A virtual environment at .venv in the current directory, or in the nearest parent directory.

If no virtual environment is found, uv will prompt the user to create one in the current directory via uv venv.

When running pip compile, uv does not require a virtual environment and will search for a Python interpreter in the following order:

• An activated virtual environment based on the VIRTUAL_ENV environment variable.
• An activated Conda environment based on the CONDA_PREFIX environment variable.
• A virtual environment at .venv in the current directory, or in the nearest parent directory.
• The Python interpreter available as python3 on macOS and Linux, or python.exe on Windows.

If a --python-version is provided to pip compile (e.g., --python-version=3.7), uv will search for a Python interpreter matching that version in the following order:

• An activated virtual environment based on the VIRTUAL_ENV environment variable.
• An activated Conda environment based on the CONDA_PREFIX environment variable.
• A virtual environment at .venv in the current directory, or in the nearest parent directory.
• The Python interpreter available as, e.g., python3.7 on macOS and Linux.
• The Python interpreter available as python3 on macOS and Linux, or python.exe on Windows.
• On Windows, the Python interpreter returned by py --list-paths that matches the requested version.

Installing into arbitrary Python environments

Since uv has no dependency on Python, it can install into virtual environments other than its own. For example, setting VIRTUAL_ENV=/path/to/venv will cause uv to install into /path/to/venv, regardless of where uv is installed. Note that if VIRTUAL_ENV is set to a directory that is not a PEP 405 compliant virtual environment, it will be ignored.

uv can also install into arbitrary, even non-virtual environments, with the --python argument provided to uv pip sync or uv pip install. For example, uv pip install --python=/path/to/python will install into the environment linked to the /path/to/python interpreter.

For convenience, uv pip install --system will install into the system Python environment. Using --system is roughly equivalent to uv pip install --python=$(which python), but note that executables that are linked to virtual environments will be skipped. Although we generally recommend using virtual environments for dependency management, --system is appropriate in continuous integration and containerized environments.

The --system flag is also used to opt in to mutating system environments. For example, the the --python argument can be used to request a Python version (e.g., --python 3.12), and uv will search for an interpreter that meets the request. If uv finds a system interpreter (e.g., /usr/lib/python3.12), then the --system flag is required to allow modification of this non-virtual Python environment. Without the --system flag, uv will ignore any interpreters that are not in virtual environments. Conversely, when the --system flag is provided, uv will ignore any interpreters that are in virtual environments.

Installing into system Python across platforms and distributions is notoriously difficult. uv supports the common cases, but will not work in all cases. For example, installing into system Python on Debian prior to Python 3.10 is unsupported due to the distribution's patching of distutils (but not sysconfig). While we always recommend the use of virtual environments, uv considers them to be required in these non-standard environments.

If uv is installed in a Python environment, e.g., with pip, it can still be used to modify other environments. However, when invoked with python -m uv, uv will default to using the parent interpreter's environment. Invoking uv via Python adds startup overhead and is not recommended for general usage.

Persistent configuration

uv supports persistent configuration at both the project- and user-level.

Specifically, uv will search for a pyproject.toml or uv.toml file in the current directory, or in the nearest parent directory.

If a pyproject.toml file is found, uv will read configuration from the [tool.uv.pip] table. For example, to set a persistent index URL, add the following to a pyproject.toml:

[tool.uv.pip]
index-url="https://test.pypi.org/simple"

(If there is no such table, the pyproject.toml file will be ignored, and uv will continue searching in the directory hierarchy.)

If a uv.toml file is found, uv will read from the [pip] table. For example:

[pip]
index-url="https://test.pypi.org/simple"

uv will also discover user-level configuration at ~/.config/uv/uv.toml (or $XDG_CONFIG_HOME/uv/uv.toml) on macOS and Linux, or %APPDATA%\uv\uv.toml on Windows. User-level configuration must use the uv.toml format, rather than the pyproject.toml format, as a pyproject.toml is intended to define a Python project.

If both project- and user-level configuration are found, the settings will be merged, with the project-level configuration taking precedence. Specifically, if a string, number, or boolean is present in both tables, the project-level value will be used, and the user-level value will be ignored. If an array is present in both tables, the arrays will be concatenated, with the project-level settings appearing earlier in the merged array.

Settings provided via environment variables take precedence over persistent configuration, and settings provided via the command line take precedence over both.

uv accepts a --isolated command-line argument which, when provided, disables the discovery of any persistent configuration.

uv also accepts a --config-file command-line argument, which accepts a path to a uv.toml to use as the configuration file. When provided, this file will be used in place of any discovered configuration files (e.g., user-level configuration will be ignored).

Git authentication

uv allows packages to be installed from Git and supports the following schemes for authenticating with private repositories.

Using SSH:

• git+ssh://git@<hostname>/... (e.g. git+ssh://git@github.com/astral-sh/uv)
• git+ssh://git@<host>/... (e.g. git+ssh://git@github.com-key-2/astral-sh/uv)

See the GitHub SSH documentation for more details on how to configure SSH.

Using a password or token:

• git+https://<user>:<token>@<hostname>/... (e.g. git+https://git:github_pat_asdf@github.com/astral-sh/uv)
• git+https://<token>@<hostname>/... (e.g. git+https://github_pat_asdf@github.com/astral-sh/uv)
• git+https://<user>@<hostname>/... (e.g. git+https://git@github.com/astral-sh/uv)

When using a GitHub personal access token, the username is arbitrary. GitHub does not support logging in with password directly, although other hosts may. If a username is provided without credentials, you will be prompted to enter them.

If there are no credentials present in the URL and authentication is needed, the Git credential helper will be queried.

HTTP authentication

uv supports credentials over HTTP when querying package registries.

Authentication can come from the following sources, in order of precedence:

• The URL, e.g., https://<user>:<password>@<hostname>/...
• A netrc configuration file
• A keyring provider (requires opt-in)

If authentication is found for a single net location (scheme, host, and port), it will be cached for the duration of the command and used for other queries to that net location. Authentication is not cached across invocations of uv.

Note --keyring-provider subprocess or UV_KEYRING_PROVIDER=subprocess must be provided to enable keyring-based authentication.

Authentication may be used for hosts specified in the following contexts:

• index-url
• extra-index-url
• find-links
• package @ https://...

See the pip compatibility guide for details on differences from pip.

Dependency caching

uv uses aggressive caching to avoid re-downloading (and re-building dependencies) that have already been accessed in prior runs.

The specifics of uv's caching semantics vary based on the nature of the dependency:

• For registry dependencies (like those downloaded from PyPI), uv respects HTTP caching headers.
• For direct URL dependencies, uv respects HTTP caching headers, and also caches based on the URL itself.
• For Git dependencies, uv caches based on the fully-resolved Git commit hash. As such, uv pip compile will pin Git dependencies to a specific commit hash when writing the resolved dependency set.
• For local dependencies, uv caches based on the last-modified time of the source archive (i.e., the local .whl or .tar.gz file). For directories, uv caches based on the last-modified time of the pyproject.toml, setup.py, or setup.cfg file.

It's safe to run multiple uv commands concurrently, even against the same virtual environment. uv's cache is designed to be thread-safe and append-only, and thus robust to multiple concurrent readers and writers. uv applies a file-based lock to the target virtual environment when installing, to avoid concurrent modifications across processes.

Note that it's not safe to modify the uv cache directly (e.g., uv cache clean) while other uv commands are running, and never safe to modify the cache directly (e.g., by removing a file or directory).

If you're running into caching issues, uv includes a few escape hatches:

• To force uv to revalidate cached data for all dependencies, run uv pip install --refresh ....
• To force uv to revalidate cached data for a specific dependency, run, e.g., uv pip install --refresh-package flask ....
• To force uv to ignore existing installed versions, run uv pip install --reinstall ....
• To clear the global cache entirely, run uv cache clean.

Resolution strategy

By default, uv follows the standard Python dependency resolution strategy of preferring the latest compatible version of each package. For example, uv pip install flask>=2.0.0 will install the latest version of Flask (at time of writing: 3.0.0).

However, uv's resolution strategy can be configured to support alternative workflows. With --resolution=lowest, uv will install the lowest compatible versions for all dependencies, both direct and transitive. Alternatively, --resolution=lowest-direct will opt for the lowest compatible versions for all direct dependencies, while using the latest compatible versions for all transitive dependencies. This distinction can be particularly useful for library authors who wish to test against the lowest supported versions of direct dependencies without restricting the versions of transitive dependencies.

For example, given the following requirements.in file:

flask>=2.0.0

Running uv pip compile requirements.in would produce the following requirements.txt file:

# This file was autogenerated by uv via the following command:
# uv pip compile requirements.in
blinker==1.7.0
 # via flask
click==8.1.7
 # via flask
flask==3.0.0
itsdangerous==2.1.2
 # via flask
jinja2==3.1.2
 # via flask
markupsafe==2.1.3
 # via
 # jinja2
 # werkzeug
werkzeug==3.0.1
 # via flask

However, uv pip compile --resolution=lowest requirements.in would instead produce:

# This file was autogenerated by uv via the following command:
# uv pip compile requirements.in --resolution=lowest
click==7.1.2
 # via flask
flask==2.0.0
itsdangerous==2.0.0
 # via flask
jinja2==3.0.0
 # via flask
markupsafe==2.0.0
 # via jinja2
werkzeug==2.0.0
 # via flask

Pre-release handling

By default, uv will accept pre-release versions during dependency resolution in two cases:

1. If the package is a direct dependency, and its version markers include a pre-release specifier (e.g., flask>=2.0.0rc1).
2. If all published versions of a package are pre-releases.

If dependency resolution fails due to a transitive pre-release, uv will prompt the user to re-run with --prerelease=allow, to allow pre-releases for all dependencies.

Alternatively, you can add the transitive dependency to your requirements.in file with a pre-release specifier (e.g., flask>=2.0.0rc1) to opt in to pre-release support for that specific dependency.

Pre-releases are notoriously difficult to model, and are a frequent source of bugs in other packaging tools. uv's pre-release handling is intentionally limited and intentionally requires user opt-in for pre-releases, to ensure correctness.

For more, see "Pre-release compatibility"

Dependency overrides

Historically, pip has supported "constraints" (-c constraints.txt), which allows users to narrow the set of acceptable versions for a given package.

uv supports constraints, but also takes this concept further by allowing users to override the acceptable versions of a package across the dependency tree via overrides (--override overrides.txt).

In short, overrides allow the user to lie to the resolver by overriding the declared dependencies of a package. Overrides are a useful last resort for cases in which the user knows that a dependency is compatible with a newer version of a package than the package declares, but the package has not yet been updated to declare that compatibility.

For example, if a transitive dependency declares pydantic>=1.0,<2.0, but the user knows that the package is compatible with pydantic>=2.0, the user can override the declared dependency with pydantic>=2.0,<3 to allow the resolver to continue.

While constraints are purely additive, and thus cannot expand the set of acceptable versions for a package, overrides can expand the set of acceptable versions for a package, providing an escape hatch for erroneous upper version bounds.

Multi-platform resolution

By default, uv's pip-compile command produces a resolution that's known to be compatible with the current platform and Python version. Unlike Poetry and PDM, uv does not yet produce a machine-agnostic lockfile (#2679).

However, uv does support resolving for alternate platforms and Python versions via the --python-platform and --python-version command line arguments.

For example, if you're running uv on macOS, but want to resolve for Linux, you can run uv pip compile --python-platform=linux requirements.in to produce a manylinux2014-compatible resolution.

Similarly, if you're running uv on Python 3.9, but want to resolve for Python 3.8, you can run uv pip compile --python-version=3.8 requirements.in to produce a Python 3.8-compatible resolution.

The --python-platform and --python-version arguments can be combined to produce a resolution for a specific platform and Python version, enabling users to generate multiple lockfiles for different environments from a single machine.

N.B. Python's environment markers expose far more information about the current machine than can be expressed by a simple --python-platform argument. For example, the platform_version marker on macOS includes the time at which the kernel was built, which can (in theory) be encoded in package requirements. uv's resolver makes a best-effort attempt to generate a resolution that is compatible with any machine running on the target --python-platform, which should be sufficient for most use cases, but may lose fidelity for complex package and platform combinations.

Time-restricted reproducible resolutions

uv supports an --exclude-newer option to limit resolution to distributions published before a specific date, allowing reproduction of installations regardless of new package releases. The date may be specified as an RFC 3339 timestamp (e.g., 2006-12-02T02:07:43Z) or UTC date in the same format (e.g., 2006-12-02).

Note the package index must support the upload-time field as specified in PEP 700. If the field is not present for a given distribution, the distribution will be treated as unavailable.

To ensure reproducibility, messages for unsatisfiable resolutions will not mention that distributions were excluded due to the --exclude-newer flag — newer distributions will be treated as if they do not exist.

Custom CA certificates

By default, uv loads certificates from the bundled webpki-roots crate. The webpki-roots are a reliable set of trust roots from Mozilla, and including them in uv improves portability and performance (especially on macOS, where reading the system trust store incurs a significant delay).

However, in some cases, you may want to use the platform's native certificate store, especially if you're relying on a corporate trust root (e.g., for a mandatory proxy) that's included in your system's certificate store. To instruct uv to use the system's trust store, run uv with the --native-tls command-line flag, or set the UV_NATIVE_TLS environment variable to true.

If a direct path to the certificate is required (e.g., in CI), set the SSL_CERT_FILE environment variable to the path of the certificate bundle, to instruct uv to use that file instead of the system's trust store.

If client certificate authentication (mTLS) is desired, set the SSL_CLIENT_CERT environment variable to the path of the PEM formatted file containing the certificate followed by the private key.

Platform support

uv has Tier 1 support for the following platforms:

• macOS (Apple Silicon)
• macOS (x86_64)
• Linux (x86_64)
• Windows (x86_64)

uv is continuously built, tested, and developed against its Tier 1 platforms. Inspired by the Rust project, Tier 1 can be thought of as "guaranteed to work".

uv has Tier 2 support ("guaranteed to build") for the following platforms:

• Linux (PPC64)
• Linux (PPC64LE)
• Linux (aarch64)
• Linux (armv7)
• Linux (i686)
• Linux (s390x)

uv ships pre-built wheels to PyPI for its Tier 1 and Tier 2 platforms. However, while Tier 2 platforms are continuously built, they are not continuously tested or developed against, and so stability may vary in practice.

Beyond the Tier 1 and Tier 2 platforms, uv is known to build on i686 Windows, and known not to build on aarch64 Windows, but does not consider either platform to be supported at this time. The minimum supported Windows version is Windows 10, following Rust's own Tier 1 support.

uv supports and is tested against Python 3.8, 3.9, 3.10, 3.11, and 3.12.

Environment variables

uv accepts the following command-line arguments as environment variables:

• UV_INDEX_URL: Equivalent to the --index-url command-line argument. If set, uv will use this URL as the base index for searching for packages.
• UV_EXTRA_INDEX_URL: Equivalent to the --extra-index-url command-line argument. If set, uv will use this space-separated list of URLs as additional indexes when searching for packages.
• UV_CACHE_DIR: Equivalent to the --cache-dir command-line argument. If set, uv will use this directory for caching instead of the default cache directory.
• UV_NO_CACHE: Equivalent to the --no-cache command-line argument. If set, uv will not use the cache for any operations.
• UV_RESOLUTION: Equivalent to the --resolution command-line argument. For example, if set to lowest-direct, uv will install the lowest compatible versions of all direct dependencies.
• UV_PRERELEASE: Equivalent to the --prerelease command-line argument. For example, if set to allow, uv will allow pre-release versions for all dependencies.
• UV_SYSTEM_PYTHON: Equivalent to the --system command-line argument. If set to true, uv will use the first Python interpreter found in the system PATH. WARNING: UV_SYSTEM_PYTHON=true is intended for use in continuous integration (CI) or containerized environments and should be used with caution, as modifying the system Python can lead to unexpected behavior.
• UV_PYTHON: Equivalent to the --python command-line argument. If set to a path, uv will use this Python interpreter for all operations.
• UV_BREAK_SYSTEM_PACKAGES: Equivalent to the --break-system-packages command-line argument. If set to true, uv will allow the installation of packages that conflict with system-installed packages. WARNING: UV_BREAK_SYSTEM_PACKAGES=true is intended for use in continuous integration (CI) or containerized environments and should be used with caution, as modifying the system Python can lead to unexpected behavior.
• UV_NATIVE_TLS: Equivalent to the --native-tls command-line argument. If set to true, uv will use the system's trust store instead of the bundled webpki-roots crate.
• UV_INDEX_STRATEGY: Equivalent to the --index-strategy command-line argument. For example, if set to unsafe-any-match, uv will consider versions of a given package available across all index URLs, rather than limiting its search to the first index URL that contains the package.
• UV_REQUIRE_HASHES: Equivalent to the --require-hashes command-line argument. If set to true, uv will require that all dependencies have a hash specified in the requirements file.
• UV_CONSTRAINT: Equivalent to the --constraint command-line argument. If set, uv will use this file as the constraints file. Uses space-separated list of files.
• UV_LINK_MODE: Equivalent to the --link-mode command-line argument. If set, uv will use this as a link mode.
• UV_NO_BUILD_ISOLATION: Equivalent to the --no-build-isolation command-line argument. If set, uv will skip isolation when building source distributions.
• UV_CUSTOM_COMPILE_COMMAND: Used to override uv in the output header of the requirements.txt files generated by uv pip compile. Intended for use-cases in which uv pip compile is called from within a wrapper script, to include the name of the wrapper script in the output file.
• UV_KEYRING_PROVIDER: Equivalent to the --keyring-provider command-line argument. If set, uv will use this value as the keyring provider.
• UV_CONFIG_FILE: Equivalent to the --config-file command-line argument. Expects a path to a local uv.toml file to use as the configuration file.
• UV_CONCURRENT_DOWNLOADS: Sets the maximum number of in-flight concurrent downloads that uv will perform at any given time.
• UV_CONCURRENT_BUILDS: Sets the maximum number of source distributions that uv will build concurrently at any given time.
• UV_CONCURRENT_INSTALLS: Used to control the number of threads used when installing and unzipping packages.
• UV_EXCLUDE_NEWER: Equivalent to the --exclude-newer command-line argument. If set, uv will exclude distributions published after the specified date.

In each case, the corresponding command-line argument takes precedence over an environment variable.

In addition, uv respects the following environment variables:

• SSL_CERT_FILE: If set, uv will use this file as the certificate bundle instead of the system's trust store.
• SSL_CLIENT_CERT: If set, uv will use this file for mTLS authentication. This should be a single file containing both the certificate and the private key in PEM format.
• RUST_LOG: If set, uv will use this value as the log level for its --verbose output. Accepts any filter compatible with the tracing_subscriber crate. For example, RUST_LOG=trace will enable trace-level logging. See the tracing documentation for more.
• HTTP_PROXY, HTTPS_PROXY, ALL_PROXY: The proxy to use for all HTTP/HTTPS requests.
• HTTP_TIMEOUT (or UV_HTTP_TIMEOUT): If set, uv will use this value (in seconds) as the timeout for HTTP reads (default: 30 s).
• PYC_INVALIDATION_MODE: The validation modes to use when run with --compile. See: PycInvalidationMode.
• VIRTUAL_ENV: Used to detect an activated virtual environment.
• CONDA_PREFIX: Used to detect an activated Conda environment.
• PROMPT: Used to detect the use of the Windows Command Prompt (as opposed to PowerShell).
• NU_VERSION: Used to detect the use of NuShell.
• FISH_VERSION: Used to detect the use of the Fish shell.
• BASH_VERSION: Used to detect the use of the Bash shell.
• ZSH_VERSION: Used to detect the use of the Zsh shell.
• MACOSX_DEPLOYMENT_TARGET: Used with --python-platform macos and related variants to set the deployment target (i.e., the minimum supported macOS version). Defaults to 12.0, the least-recent non-EOL macOS version at time of writing.
• NO_COLOR: Disable colors. Takes precedence over FORCE_COLOR. See no-color.org.
• FORCE_COLOR: Enforce colors regardless of TTY support. See force-color.org.

Versioning

uv uses a custom versioning scheme in which the minor version number is bumped for breaking changes, and the patch version number is bumped for bug fixes, enhancements, and other non-breaking changes.

uv does not yet have a stable API; once uv's API is stable (v1.0.0), the versioning scheme will adhere to Semantic Versioning.

Acknowledgements

uv's dependency resolver uses PubGrub under the hood. We're grateful to the PubGrub maintainers, especially Jacob Finkelman, for their support.

uv's Git implementation is based on Cargo.

Some of uv's optimizations are inspired by the great work we've seen in pnpm, Orogene, and Bun. We've also learned a lot from Nathaniel J. Smith's Posy and adapted its trampoline for Windows support.

License

uv is licensed under either of

• Apache License, Version 2.0, (LICENSE-APACHE or https://www.apache.org/licenses/LICENSE-2.0)
• MIT license (LICENSE-MIT or https://opensource.org/licenses/MIT)

at your option.

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in uv by you, as defined in the Apache-2.0 license, shall be dually licensed as above, without any additional terms or conditions.

Verified details

These details have been verified by PyPI

Maintainers

👁 Avatar for astral-bot from gravatar.com
astral-bot 👁 Avatar for crmarsh from gravatar.com
crmarsh 👁 Avatar for sarasklenka from gravatar.com
sarasklenka 👁 Avatar for zanie from gravatar.com
zanie

Unverified details

These details have not been verified by PyPI

Project links

• Homepage
• Documentation
• Repository

• Download URL: uv-0.2.15.tar.gz
• Upload date: Jun 24, 2024
• Size: 924.7 kB
• Tags: Source
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.1.0 CPython/3.12.4

Hashes for uv-0.2.15.tar.gz

Algorithm	Hash digest
SHA256	3eb2832ad6a600c117bbbd5faf8d2bbe6b3c0817cebde9fb9e7514dd4cce4efb
MD5	f61d8c302611c30ec0b657a76378f315
BLAKE2b-256	597ff1e8d08a0f32b04c91828e32fad0712ff2a67d8c8cdddc094d6a4048d323

See more details on using hashes here.

• Download URL: uv-0.2.15-py3-none-win_amd64.whl
• Upload date: Jun 24, 2024
• Size: 11.6 MB
• Tags: Python 3, Windows x86-64
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.1.0 CPython/3.12.4

Hashes for uv-0.2.15-py3-none-win_amd64.whl

Algorithm	Hash digest
SHA256	687dbe01b557a5272197955af6310dd50b3999ad12dde1c09dfd385755d7d8ab
MD5	30dbe7dcad513beafb344633f90a79b2
BLAKE2b-256	4b89280feb76982bdfe295bb67450abfa215e4454207687a5bb5a669295e971e

See more details on using hashes here.

• Download URL: uv-0.2.15-py3-none-win32.whl
• Upload date: Jun 24, 2024
• Size: 10.1 MB
• Tags: Python 3, Windows x86
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.1.0 CPython/3.12.4

Hashes for uv-0.2.15-py3-none-win32.whl

Algorithm	Hash digest
SHA256	ddadc472eeda3861116542015869ecef1dbf920e85a4f6ebea350250edcde26a
MD5	79e6a9249a57df3588e78368318444f0
BLAKE2b-256	4a4ae6c458902cac7205582a0632d0ddbf513536c83abb3801f4a039f56e5647

See more details on using hashes here.

• Download URL: uv-0.2.15-py3-none-musllinux_1_1_x86_64.whl
• Upload date: Jun 24, 2024
• Size: 12.0 MB
• Tags: Python 3, musllinux: musl 1.1+ x86-64
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.1.0 CPython/3.12.4

Hashes for uv-0.2.15-py3-none-musllinux_1_1_x86_64.whl

Algorithm	Hash digest
SHA256	dad5e7424b71fd4cb47252327ba49fcfe90660ed524e678bfb1b03c37502983c
MD5	84b1b2ebd176e0735e1561890417d223
BLAKE2b-256	269d287b13e745760c355b427588f522481de75a4e7a763f5cf0257181511cf2

See more details on using hashes here.

• Download URL: uv-0.2.15-py3-none-musllinux_1_1_ppc64le.whl
• Upload date: Jun 24, 2024
• Size: 13.1 MB
• Tags: Python 3, musllinux: musl 1.1+ ppc64le
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.1.0 CPython/3.12.4

Hashes for uv-0.2.15-py3-none-musllinux_1_1_ppc64le.whl

Algorithm	Hash digest
SHA256	3740cf68b429fd5e32d9555e34dbf986d6524e33fc4e6156ebc0c55d946b6a94
MD5	51786b5cd4c3b985899d3a58bea0ed87
BLAKE2b-256	c4569fa094c0bf82fcc3abb6481a09b840a538bd08991df9d0953218fb182a93

See more details on using hashes here.

• Download URL: uv-0.2.15-py3-none-musllinux_1_1_i686.whl
• Upload date: Jun 24, 2024
• Size: 11.5 MB
• Tags: Python 3, musllinux: musl 1.1+ i686
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.1.0 CPython/3.12.4

Hashes for uv-0.2.15-py3-none-musllinux_1_1_i686.whl

Algorithm	Hash digest
SHA256	4be4a05ffec2dcedea9661a5f4a6b81cc14e43ee9579e7a6a66358ea7af92220
MD5	e22518621714eef5928c7fbd1acf6d02
BLAKE2b-256	3dd89d386acc9a658438020961fbabe84445f87b6ebb225a4efe589cf34dd10d

See more details on using hashes here.

• Download URL: uv-0.2.15-py3-none-musllinux_1_1_armv7l.whl
• Upload date: Jun 24, 2024
• Size: 12.4 MB
• Tags: Python 3, musllinux: musl 1.1+ ARMv7l
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.1.0 CPython/3.12.4

Hashes for uv-0.2.15-py3-none-musllinux_1_1_armv7l.whl

Algorithm	Hash digest
SHA256	20cb1cc98e4cd02a3b8439994309341825fa6b2f49071f8c2f02a256f7b635a2
MD5	e6e87e33fd7fdb909bfda59eb16f78be
BLAKE2b-256	9121b919ba2076dd2b4aa2a40fc5f1fca63fbb266dff17517ec739e6bf02849e

See more details on using hashes here.

• Download URL: uv-0.2.15-py3-none-manylinux_2_28_aarch64.whl
• Upload date: Jun 24, 2024
• Size: 11.0 MB
• Tags: Python 3, manylinux: glibc 2.28+ ARM64
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.1.0 CPython/3.12.4

Hashes for uv-0.2.15-py3-none-manylinux_2_28_aarch64.whl

Algorithm	Hash digest
SHA256	e791ba598329e064c6690550a9af7798292c5e3548c757688af752063293fe7c
MD5	061bb5c7afeaa0391620bf9b099076e8
BLAKE2b-256	f5e303ff5b87ffce05bfb5508dde099ce7260f6b1a4dcaf89532f0a52888939f

See more details on using hashes here.

• Download URL: uv-0.2.15-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
• Upload date: Jun 24, 2024
• Size: 11.9 MB
• Tags: Python 3, manylinux: glibc 2.17+ x86-64
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.1.0 CPython/3.12.4

Hashes for uv-0.2.15-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Algorithm	Hash digest
SHA256	193e5e9d570e035bde6be95b7d57cc87b97df8603f69a1245029b98351420dcc
MD5	127a0c1b6dfa1cf8e5d7c2928fd1ba82
BLAKE2b-256	41665aa271f738f9c9f8040821f7f372810f6e678b646ca96888de8076dd5d2c

See more details on using hashes here.

• Download URL: uv-0.2.15-py3-none-manylinux_2_17_s390x.manylinux2014_s390x.whl
• Upload date: Jun 24, 2024
• Size: 12.8 MB
• Tags: Python 3, manylinux: glibc 2.17+ s390x
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.1.0 CPython/3.12.4

Hashes for uv-0.2.15-py3-none-manylinux_2_17_s390x.manylinux2014_s390x.whl

Algorithm	Hash digest
SHA256	76cd6427acbe87a29538a76c2c87f6fd1c50e0e204984d3c380501c0480631db
MD5	d501c498df924ff58a83519ad5d7d226
BLAKE2b-256	5883a028cff62b3b1f5eb9f0efc835a4e0256b2b486818ca6e9ea2c0a3d3ded2

See more details on using hashes here.

• Download URL: uv-0.2.15-py3-none-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl
• Upload date: Jun 24, 2024
• Size: 12.1 MB
• Tags: Python 3, manylinux: glibc 2.17+ ppc64le
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.1.0 CPython/3.12.4

Hashes for uv-0.2.15-py3-none-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl

Algorithm	Hash digest
SHA256	dd86cb926070bd744372ac06f492863dbe427312faf0ad1d5293d496328caf38
MD5	da7212080edf73b98b50307de99ab416
BLAKE2b-256	dab47ed97f1f920349e90b52477269662b1fb7df9f031d2b1cc3883eb547803a

See more details on using hashes here.

• Download URL: uv-0.2.15-py3-none-manylinux_2_17_ppc64.manylinux2014_ppc64.whl
• Upload date: Jun 24, 2024
• Size: 12.6 MB
• Tags: Python 3, manylinux: glibc 2.17+ ppc64
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.1.0 CPython/3.12.4

Hashes for uv-0.2.15-py3-none-manylinux_2_17_ppc64.manylinux2014_ppc64.whl

Algorithm	Hash digest
SHA256	96b5470903dd772c7b2316c3540c78b6df5c4ec1b621d92327c7df48a6358fce
MD5	c36891b1cf9826b09a623b87c8206794
BLAKE2b-256	31ddf32a380e651ae4f18c1d38c2b7e64920be89bae7fdc576475ff331c9df15

See more details on using hashes here.

• Download URL: uv-0.2.15-py3-none-manylinux_2_17_i686.manylinux2014_i686.whl
• Upload date: Jun 24, 2024
• Size: 12.3 MB
• Tags: Python 3, manylinux: glibc 2.17+ i686
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.1.0 CPython/3.12.4

Hashes for uv-0.2.15-py3-none-manylinux_2_17_i686.manylinux2014_i686.whl

Algorithm	Hash digest
SHA256	7bb79bc088dc43c9932c7b04ac76c436e5e705002f11edf530ded48254847c53
MD5	68b869f9d0e00663b090a9f052971234
BLAKE2b-256	579cc2a1b1dbee2526b4ed3e3912d4bca5f02f5b9932b581ffe36780d50f35b3

See more details on using hashes here.

• Download URL: uv-0.2.15-py3-none-manylinux_2_17_armv7l.manylinux2014_armv7l.whl
• Upload date: Jun 24, 2024
• Size: 10.3 MB
• Tags: Python 3, manylinux: glibc 2.17+ ARMv7l
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.1.0 CPython/3.12.4

Hashes for uv-0.2.15-py3-none-manylinux_2_17_armv7l.manylinux2014_armv7l.whl

Algorithm	Hash digest
SHA256	9d263243c1b81b0417ee98084101ef6a2a3bd8fe2784b7bfbca9d59892594a41
MD5	14db67bab0036a552417243a849ff63e
BLAKE2b-256	8ab0893292f9d0afd70a9c7fb4676b2a3b0a293583d72f2ce7a8fce7e3e2f647

See more details on using hashes here.

• Download URL: uv-0.2.15-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.musllinux_1_1_aarch64.whl
• Upload date: Jun 24, 2024
• Size: 13.1 MB
• Tags: Python 3, manylinux: glibc 2.17+ ARM64, musllinux: musl 1.1+ ARM64
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.1.0 CPython/3.12.4

Hashes for uv-0.2.15-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.musllinux_1_1_aarch64.whl

Algorithm	Hash digest
SHA256	70659ecc54ce5aaf48cf7897d62f028e93e5ba80d2712052a62ccf4f1592ab0e
MD5	3f23750493ab53f425d6ed92f1fb0b38
BLAKE2b-256	a80d3f4c1e122a6f7faacef589a36dc0c3fdda6a3d36fedb0fe773fb89e7841b

See more details on using hashes here.

• Download URL: uv-0.2.15-py3-none-macosx_11_0_arm64.whl
• Upload date: Jun 24, 2024
• Size: 10.8 MB
• Tags: Python 3, macOS 11.0+ ARM64
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.1.0 CPython/3.12.4

Hashes for uv-0.2.15-py3-none-macosx_11_0_arm64.whl

Algorithm	Hash digest
SHA256	72edbdbdc185c6ea20b789e8ebb2cb2ceb4903a224e9f917fdedc27489a92bb0
MD5	d9023028699347f4da9b8f5609823c45
BLAKE2b-256	1547bd2d49231345aead441ef48923ea8ce42655d75d0eb176be2326a988f21e

See more details on using hashes here.

• Download URL: uv-0.2.15-py3-none-macosx_10_12_x86_64.whl
• Upload date: Jun 24, 2024
• Size: 11.4 MB
• Tags: Python 3, macOS 10.12+ x86-64
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.1.0 CPython/3.12.4

Hashes for uv-0.2.15-py3-none-macosx_10_12_x86_64.whl

Algorithm	Hash digest
SHA256	3f783c0e31ecb37091bc24d6968d6b91b5e31b816c6418e74e291b49b2cc7ab6
MD5	86bc683f9cc427da2270ecb18539073f
BLAKE2b-256	082855826f2acc67ad9b6d4562cc732a6d743910bed4a9190b7ad5a739864e58

See more details on using hashes here.

• Download URL: uv-0.2.15-py3-none-linux_armv6l.whl
• Upload date: Jun 24, 2024
• Size: 10.4 MB
• Tags: Python 3
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.1.0 CPython/3.12.4

Hashes for uv-0.2.15-py3-none-linux_armv6l.whl

Algorithm	Hash digest
SHA256	4742f3e96ed927919783a6a67e6c9f14416745a57fac926e173783293c63c9ae
MD5	dd1be425bd92172f139a7c9c36184764
BLAKE2b-256	b512f2a045874453db1259c53d3d82890cb9f3702642c3ab044d4066af218c76

See more details on using hashes here.