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

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.

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

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.

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

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_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: 30s).
• 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.7.tar.gz
• Upload date: Jun 5, 2024
• Size: 842.5 kB
• Tags: Source
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.3

Hashes for uv-0.2.7.tar.gz

Algorithm	Hash digest
SHA256	b7b6e25836c618e67f4a8d288b08614d811c63e64dd352b79b78aca9375dbe43
MD5	d0d29cdf98868e55c376d8d0051ff41b
BLAKE2b-256	89287642568a42a85e76d1806df6499ff0e279205bf5d998c6e95d1b70f56fce

See more details on using hashes here.

• Download URL: uv-0.2.7-py3-none-win_amd64.whl
• Upload date: Jun 5, 2024
• Size: 10.2 MB
• Tags: Python 3, Windows x86-64
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.3

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

Algorithm	Hash digest
SHA256	ed9b8829ca4817f3d5c295c284eaff1b3c0f2417bec2962bcdb61fa214e460cf
MD5	aa288b61e0d6eb54533fbac95aeb33e9
BLAKE2b-256	d1a383c6e6dae64a33a7bc9daa485a2960a828cb78dc8f8c74f72808442dc9fb

See more details on using hashes here.

• Download URL: uv-0.2.7-py3-none-win32.whl
• Upload date: Jun 5, 2024
• Size: 9.0 MB
• Tags: Python 3, Windows x86
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.3

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

Algorithm	Hash digest
SHA256	59ef8f4ce8dc47c0c7dd71bb8ecd7ab05ff1142c679bafcfc400301b71b184b4
MD5	9030d0075a5f9573a6a26440bc9e2c3f
BLAKE2b-256	1b7f36365997cbd46300d7013c633b4f97f9107cb0e1e229418c3188a37007e4

See more details on using hashes here.

• Download URL: uv-0.2.7-py3-none-musllinux_1_1_x86_64.whl
• Upload date: Jun 5, 2024
• Size: 10.6 MB
• Tags: Python 3, musllinux: musl 1.1+ x86-64
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.3

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

Algorithm	Hash digest
SHA256	a575440461016d1f33ddff2fcfe9cb0023a2496526d817252d23fd0dcf686674
MD5	da398a9da6372255738141127d25eca0
BLAKE2b-256	6f3bc02543156d6a462b764288fbfba46a5e5dd9870d16f2887dd045d6640be9

See more details on using hashes here.

• Download URL: uv-0.2.7-py3-none-musllinux_1_1_ppc64le.whl
• Upload date: Jun 5, 2024
• Size: 11.9 MB
• Tags: Python 3, musllinux: musl 1.1+ ppc64le
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.3

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

Algorithm	Hash digest
SHA256	13c2231856197e2438a0ce3303202be4d3375e0fc9a524e47d3098c35bf95031
MD5	938f071393219dc913e9cff872059b0a
BLAKE2b-256	8ad5ea2a5c4551f076a3990652fe7e246219424a24d28b0481096eb4a72a0925

See more details on using hashes here.

• Download URL: uv-0.2.7-py3-none-musllinux_1_1_i686.whl
• Upload date: Jun 5, 2024
• Size: 10.1 MB
• Tags: Python 3, musllinux: musl 1.1+ i686
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.3

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

Algorithm	Hash digest
SHA256	3a88878e731edab1b9a991bdb490d9321bb233908cbe338d2ef2bd2db553d611
MD5	cc0e52bf9eebfa90ba49eb23f3a699bb
BLAKE2b-256	bb310923db9c46ebdb6157fd3454fac2fcafdd00b33ac2aa6118c57533bea6a4

See more details on using hashes here.

• Download URL: uv-0.2.7-py3-none-musllinux_1_1_armv7l.whl
• Upload date: Jun 5, 2024
• Size: 9.0 MB
• Tags: Python 3, musllinux: musl 1.1+ ARMv7l
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.3

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

Algorithm	Hash digest
SHA256	bf08aea2d52dffab9ba455a85b3130eecc6096788fe00492e4fce1b0f8feb3d6
MD5	05cc33ab884add95e126eb70824c0c2c
BLAKE2b-256	391ff998c78d27b025ef3f9d9d20a57a80871935091603b54a791cadbdd6481d

See more details on using hashes here.

• Download URL: uv-0.2.7-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
• Upload date: Jun 5, 2024
• Size: 10.6 MB
• Tags: Python 3, manylinux: glibc 2.17+ x86-64
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.3

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

Algorithm	Hash digest
SHA256	79bd1b2fecbdb534584be3cfd4322339c77c75f08d479fa2c777c92eb2671317
MD5	2a828f31665a02c45fe607e98e2d6d64
BLAKE2b-256	5721dc8a502fbeb99838f18e130534f8653dcca1f47481750289eb159743ce66

See more details on using hashes here.

• Download URL: uv-0.2.7-py3-none-manylinux_2_17_s390x.manylinux2014_s390x.whl
• Upload date: Jun 5, 2024
• Size: 11.3 MB
• Tags: Python 3, manylinux: glibc 2.17+ s390x
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.3

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

Algorithm	Hash digest
SHA256	77bf149b511b3a42a6dbd831435a7c00d95562598abf60f007e6d42e26011dff
MD5	b1481829719c26bc6d55b05675a959e5
BLAKE2b-256	1e3346e8ad77230282bee18a05abab41f68e38f8d4f9a5a976792e514c62a288

See more details on using hashes here.

• Download URL: uv-0.2.7-py3-none-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl
• Upload date: Jun 5, 2024
• Size: 10.7 MB
• Tags: Python 3, manylinux: glibc 2.17+ ppc64le
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.3

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

Algorithm	Hash digest
SHA256	9c95b3ed1071b0ba2e8bb8dafd77a8b8fd19d3cd116a147ff8155522c76f87d4
MD5	7794c6971c109287413ef69cd9064d08
BLAKE2b-256	664a733d00f7aaee01ac6a35dc3e45d2f1fb2c0d14a43e1c12d91af309fd77aa

See more details on using hashes here.

• Download URL: uv-0.2.7-py3-none-manylinux_2_17_ppc64.manylinux2014_ppc64.whl
• Upload date: Jun 5, 2024
• Size: 11.2 MB
• Tags: Python 3, manylinux: glibc 2.17+ ppc64
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.3

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

Algorithm	Hash digest
SHA256	a7e0c6b3baf2ff350edb15af5c66f42b3db54539b8302690c70922764f425b84
MD5	6a630b4257be57accffaaf12469af64a
BLAKE2b-256	c4de6dc288572bb2e8d75f46d6d759aab3091c2619c50844a54580c82dc694ad

See more details on using hashes here.

• Download URL: uv-0.2.7-py3-none-manylinux_2_17_i686.manylinux2014_i686.whl
• Upload date: Jun 5, 2024
• Size: 10.9 MB
• Tags: Python 3, manylinux: glibc 2.17+ i686
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.3

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

Algorithm	Hash digest
SHA256	fc2df0d7f349e00881f3d13bb64c07e66eb4b50bad6628875543a0acce79a919
MD5	cef525e0ff3c74f43a312fcdd23b5093
BLAKE2b-256	81922e3c5324a666a4cf450855453f5eb9bab78003dbee654a85889d85fd747c

See more details on using hashes here.

• Download URL: uv-0.2.7-py3-none-manylinux_2_17_armv7l.manylinux2014_armv7l.whl
• Upload date: Jun 5, 2024
• Size: 9.1 MB
• Tags: Python 3, manylinux: glibc 2.17+ ARMv7l
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.3

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

Algorithm	Hash digest
SHA256	e7cfbffd7c5d3e1ba6c62810afa71ffbd6a3e9c131494a5d2d47d3522ddae165
MD5	8164539c0cb69fdc8fca2fbea8320162
BLAKE2b-256	c36faecccbdfa685f78cf6332b995149322b0a151756d23e14f823b928250247

See more details on using hashes here.

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

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

Algorithm	Hash digest
SHA256	4eb2aca31c1de4a20c136f598465e9bf596ff9a513f30476cdeafe789654cc11
MD5	3208d7a67c411cde1c2df76333d6907d
BLAKE2b-256	9b8c781f41eb564ebff7806b41249f550e734c700f884dfd6dac41557c314851

See more details on using hashes here.

• Download URL: uv-0.2.7-py3-none-macosx_11_0_arm64.whl
• Upload date: Jun 5, 2024
• Size: 9.6 MB
• Tags: Python 3, macOS 11.0+ ARM64
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.3

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

Algorithm	Hash digest
SHA256	6667ed2de9c8e7c37529e7d4457cd8fc7627dc3d2c029128c52f1b6aef102549
MD5	b59fe6a6790ac1849da18dc0e0651a1d
BLAKE2b-256	50e73f297292ab0569a76d1a5ecad261cc6ad76ba9f58c3f24266ef08632100d

See more details on using hashes here.

• Download URL: uv-0.2.7-py3-none-macosx_10_12_x86_64.whl
• Upload date: Jun 5, 2024
• Size: 10.1 MB
• Tags: Python 3, macOS 10.12+ x86-64
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.3

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

Algorithm	Hash digest
SHA256	8e01e091e6c228df2a17f0ca151300d2a8691067b7efaf0075ed46ee42ef62f9
MD5	9418cfc62fe8871c0624b2cd10324b67
BLAKE2b-256	4b764619521cea636d35322edcc4886c25cfec8284e1206bf45b629b20d2aac1

See more details on using hashes here.

• Download URL: uv-0.2.7-py3-none-linux_armv6l.whl
• Upload date: Jun 5, 2024
• Size: 9.1 MB
• Tags: Python 3
• Uploaded using Trusted Publishing? Yes
• Uploaded via: twine/5.0.0 CPython/3.12.3

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

Algorithm	Hash digest
SHA256	96d1dc1b20f388df663b308e904df9eb8b83a98a8cc6d2002513014efa352aa2
MD5	b05d7f32aa7506e06b5ca48fac6403b6
BLAKE2b-256	a883902ff630cbd1c1d237b13a5fb8f08170c79adc9273fa02bd8ff9e1a886b3

See more details on using hashes here.