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"

# With pip.
pipinstalluv

# With pipx.
pipxinstalluv

# With Homebrew.
brewinstalluv

# With Pacman.
pacman-Suv

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 even 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, no matter where uv is installed.

uv can also install into arbitrary, even non-virtual environments by providing a --python argument 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, as an approximate shorthand for, e.g., uv pip install --python=$(which python3). Though we generally recommend the use of virtual environments for dependency management, --system is intended to enable the use of uv in continuous integration and containerized 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.

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 setup.py or pyproject.toml file.

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 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-version resolution

uv's pip-compile command produces a resolution that's known to be compatible with the current platform and Python version. Unlike Poetry, PDM, and other package managers, uv does not yet produce a machine-agnostic lockfile.

However, uv does support resolving for alternate Python versions via the --python-version command line argument. For example, 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.

Reproducible resolution

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 a 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.

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.

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) environments and should be used with caution, as it can modify the system Python installation.
• 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.

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.
• 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_TIMEOUT (or UV_HTTP_TIMEOUT): If set, uv will use this value (in seconds) as the timeout for HTTP requests.
• 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 appropriate activation script after generating a virtual environment.
• NU_VERSION: Used to detect the appropriate activation script after generating a virtual environment.

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.

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.1.28.tar.gz
• Upload date: Apr 2, 2024
• Size: 623.5 kB
• Tags: Source
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.2

Hashes for uv-0.1.28.tar.gz

Algorithm	Hash digest
SHA256	8877968a53eba9d76b8dcac950be90d745d81e2ccb8cc82c9a589634147d4874
MD5	6c09b748a1d08be51d5234264cb54bfa
BLAKE2b-256	aee992374f8b15efa149e26fe144d0cc34dc92f2614cf32e4e223bac574bbf00

See more details on using hashes here.

• Download URL: uv-0.1.28-py3-none-win_amd64.whl
• Upload date: Apr 2, 2024
• Size: 9.4 MB
• Tags: Python 3, Windows x86-64
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.2

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

Algorithm	Hash digest
SHA256	b3a2135432901a1214c732fb6185095ae1c12ecd6f1e36fa6a0629ca3bd964ad
MD5	d01625016dd0b838f18c034bd12f1b9c
BLAKE2b-256	16c437325e158cdc88a00630de704f9ed7e9140bd5f171cb77fbef439142f6ec

See more details on using hashes here.

• Download URL: uv-0.1.28-py3-none-win32.whl
• Upload date: Apr 2, 2024
• Size: 8.2 MB
• Tags: Python 3, Windows x86
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.2

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

Algorithm	Hash digest
SHA256	b35a9acc8c5b0dd8cd3aebb6b6a9d19b274004bec0a71cada9fca14993a0ee25
MD5	b4857949032bf5abc69a7f7f96adf6f5
BLAKE2b-256	f606e06c3e0cec6280a9d450182b667f3b258e93e52f863494f95a718195de59

See more details on using hashes here.

• Download URL: uv-0.1.28-py3-none-musllinux_1_2_x86_64.whl
• Upload date: Apr 2, 2024
• Size: 11.6 MB
• Tags: Python 3, musllinux: musl 1.2+ x86-64
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.2

Hashes for uv-0.1.28-py3-none-musllinux_1_2_x86_64.whl

Algorithm	Hash digest
SHA256	7efbb437bca88efffcaba803d272e2ed73e417c3da09b3c55594656450ed282a
MD5	22e46f9f0ec5de1e563a7afbe156a2ad
BLAKE2b-256	a7c722a81067015163b8f528817616292e60785f1add03a0a9852b84edb70873

See more details on using hashes here.

• Download URL: uv-0.1.28-py3-none-musllinux_1_2_i686.whl
• Upload date: Apr 2, 2024
• Size: 11.0 MB
• Tags: Python 3, musllinux: musl 1.2+ i686
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.2

Hashes for uv-0.1.28-py3-none-musllinux_1_2_i686.whl

Algorithm	Hash digest
SHA256	802a71431009d037b25279ecaaeb198350050c74bf6feefa5d148cfec9dd1eb6
MD5	085a481643574611df98899fd8cd1fa1
BLAKE2b-256	c494e7e480d865a60cb18e32ab89ba3499d6031f633b1cd9671a7bf599db8f60

See more details on using hashes here.

• Download URL: uv-0.1.28-py3-none-musllinux_1_2_armv7l.whl
• Upload date: Apr 2, 2024
• Size: 9.7 MB
• Tags: Python 3, musllinux: musl 1.2+ ARMv7l
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.2

Hashes for uv-0.1.28-py3-none-musllinux_1_2_armv7l.whl

Algorithm	Hash digest
SHA256	602883ff3c709a9b0261949c2544e95a52a02806d6fd26530a18b8e6d3ce201e
MD5	923cd5108202f31a086a7d4c98bedc23
BLAKE2b-256	395ebc3a6a08fae2bc094bca3969a64414797960a3379b73064605f53db448b8

See more details on using hashes here.

• Download URL: uv-0.1.28-py3-none-musllinux_1_2_aarch64.whl
• Upload date: Apr 2, 2024
• Size: 11.0 MB
• Tags: Python 3, musllinux: musl 1.2+ ARM64
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.2

Hashes for uv-0.1.28-py3-none-musllinux_1_2_aarch64.whl

Algorithm	Hash digest
SHA256	242116fa76280bc432c903fc6e7179100186a77cd448dbe1b28f08991a2e9897
MD5	eb0b33629f60480cac3944ca7ed2d602
BLAKE2b-256	8b41c9c37ec2016c08844775f6ab8bce3e886fe88421505a4f9e6495ffa1b943

See more details on using hashes here.

• Download URL: uv-0.1.28-py3-none-manylinux_2_28_aarch64.whl
• Upload date: Apr 2, 2024
• Size: 11.1 MB
• Tags: Python 3, manylinux: glibc 2.28+ ARM64
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.2

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

Algorithm	Hash digest
SHA256	1183224cfaced630a02b5e004c9858928c2edb730ccbdda99e099258dfebff0e
MD5	38515262105c7634580c0135ef327c09
BLAKE2b-256	4a052b7835c9e58b375e072281f507b14227113031f739ef9d46057d408502ed

See more details on using hashes here.

• Download URL: uv-0.1.28-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
• Upload date: Apr 2, 2024
• Size: 11.5 MB
• Tags: Python 3, manylinux: glibc 2.17+ x86-64
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.2

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

Algorithm	Hash digest
SHA256	c4a2a3f2654102289f19d518cfa1e5e3df949de7c0919cf40f2aac596f83c9bc
MD5	76c1ccfe51a700f03764900293cc2138
BLAKE2b-256	bf23e65d0f8cd4d9904a82a616c265bb30ccc802b16226b964e9f668da26dc2b

See more details on using hashes here.

• Download URL: uv-0.1.28-py3-none-manylinux_2_17_s390x.manylinux2014_s390x.whl
• Upload date: Apr 2, 2024
• Size: 12.3 MB
• Tags: Python 3, manylinux: glibc 2.17+ s390x
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.2

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

Algorithm	Hash digest
SHA256	01a2da29191ccc5141f28557a9074bfdce7178a80a553658395bd53c54eb4765
MD5	cdde057a4d5b39091975918db7b63eae
BLAKE2b-256	25b70eab2e50b7c70243524d4e08d5fa6c0c34a6d47982795774189e77bb4d95

See more details on using hashes here.

• Download URL: uv-0.1.28-py3-none-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl
• Upload date: Apr 2, 2024
• Size: 11.9 MB
• Tags: Python 3, manylinux: glibc 2.17+ ppc64le
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.2

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

Algorithm	Hash digest
SHA256	f3765e367d6a8578a89e7da5972693cd4f6d223a567bf4ddd3ae1681b807f87b
MD5	4ea43ed500c24c58cccd38b1a8e4ca8a
BLAKE2b-256	25975600bd04216f0011a46c9c3432d9286b904443c07cd548a2a104f54cd59e

See more details on using hashes here.

• Download URL: uv-0.1.28-py3-none-manylinux_2_17_ppc64.manylinux2014_ppc64.whl
• Upload date: Apr 2, 2024
• Size: 12.4 MB
• Tags: Python 3, manylinux: glibc 2.17+ ppc64
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.2

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

Algorithm	Hash digest
SHA256	d1dcb71540952a4129b50b734451f9b054853c2c84d6e25994a737682d64e091
MD5	033c6af02afc5c95dd3a85c8e4f0f5db
BLAKE2b-256	d0af0d7b9fbb63230663f9df040d97c501edc6ab957943404e225798ef86cb48

See more details on using hashes here.

• Download URL: uv-0.1.28-py3-none-manylinux_2_17_i686.manylinux2014_i686.whl
• Upload date: Apr 2, 2024
• Size: 11.6 MB
• Tags: Python 3, manylinux: glibc 2.17+ i686
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.2

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

Algorithm	Hash digest
SHA256	94baef28b6b2da43f8c2facc9ab4e199c3795b6467e46f5e7f05fbbd81f66aa2
MD5	325afe1a4f946be5411329fa035cf47a
BLAKE2b-256	d114ef140ff01eb2f99c1ecbfbbcbbb8f09ef206b5ebb565f4d540b131fbe3db

See more details on using hashes here.

• Download URL: uv-0.1.28-py3-none-manylinux_2_17_armv7l.manylinux2014_armv7l.whl
• Upload date: Apr 2, 2024
• Size: 9.7 MB
• Tags: Python 3, manylinux: glibc 2.17+ ARMv7l
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.2

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

Algorithm	Hash digest
SHA256	af86dbe3645ca83ceb0f5e20e90aea24f554be388bfdc3e29519b9e8f7664fd9
MD5	ba539dd8ec08cfef1469708df6d2865d
BLAKE2b-256	2f35d5c0a1494ddca86ef70895859eb11941bd9324176f5947691e9608e1011e

See more details on using hashes here.

• Download URL: uv-0.1.28-py3-none-macosx_10_12_x86_64.whl
• Upload date: Apr 2, 2024
• Size: 10.5 MB
• Tags: Python 3, macOS 10.12+ x86-64
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.2

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

Algorithm	Hash digest
SHA256	e200b3253ba255d1901bcd98e8f17518ac8f033810c2cc112aaa3922079aa579
MD5	a4ff49bc92a544a3095bdbc748cf87e0
BLAKE2b-256	cbddb546dd628f12af3f2e4cf952014e36e685499ba10d140fa327bce3967172

See more details on using hashes here.

• Download URL: uv-0.1.28-py3-none-macosx_10_12_x86_64.macosx_11_0_arm64.macosx_10_12_universal2.whl
• Upload date: Apr 2, 2024
• Size: 21.0 MB
• Tags: Python 3, macOS 10.12+ universal2 (ARM64, x86-64), macOS 10.12+ x86-64, macOS 11.0+ ARM64
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.2

Hashes for uv-0.1.28-py3-none-macosx_10_12_x86_64.macosx_11_0_arm64.macosx_10_12_universal2.whl

Algorithm	Hash digest
SHA256	b721cefd84f70b7511bb4bc271d3181bb62d808bbe5ecb5096eb1fdda8a2a829
MD5	4315d58eabe542e50fd210c20229fba7
BLAKE2b-256	0bf07e45a02b9dd0f9f9fe3508526eca93174b55b32f0ca0097ec607b16dcf78

See more details on using hashes here.

• Download URL: uv-0.1.28-py3-none-linux_armv6l.whl
• Upload date: Apr 2, 2024
• Size: 9.8 MB
• Tags: Python 3
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.2

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

Algorithm	Hash digest
SHA256	844945b3ec1c44206a87da40f6b3ddeaf066c2920dcb7b723202df0d52c3b234
MD5	36def257c9dc95e2b17ac263956f8ddf
BLAKE2b-256	8b1bc6cb71557abf10b693c3c732a3fec7b25b0554c9375f24e071af8e7879f4

See more details on using hashes here.