PEX
Overview
pex is a library for generating .pex (Python EXecutable) files which are executable Python environments in the spirit of virtualenvs. pex is an expansion upon the ideas outlined in PEP 441 and makes the deployment of Python applications as simple as cp. pex files may even include multiple platform-specific Python distributions, meaning that a single pex file can be portable across Linux and OS X.
pex files can be built using the pex tool. Build systems such as Pants, Buck, and {py}gradle also support building .pex files directly.
Still unsure about what pex does or how it works? Watch this quick lightning talk: WTF is PEX?.
pex is licensed under the Apache2 license.
Installation
To install pex, simply
$ pip install pexYou can also build pex in a git clone using uv:
$ uv run dev-cmd package
$ cp dist/pex ~/binThis builds a pex binary in dist/pex that can be copied onto your $PATH. The advantage to this approach is that it keeps your Python environment as empty as possible and is more in-line with what pex does philosophically.
Simple Examples
Launch an interpreter with requests, flask and psutil in the environment:
$ pex requests flask 'psutil>2,<3'Save Dependencies From Pip
Or instead freeze your current virtualenv via requirements.txt and execute it anywhere:
$ pex $(pip freeze) -o my_virtualenv.pex
$ deactivate
$ ./my_virtualenv.pexEphemeral Environments
Run webserver.py in an environment containing flask as a quick way to experiment:
$ pex flask -- webserver.pyLaunch Sphinx in an ephemeral pex environment using the Sphinx entry point sphinx:main:
$ pex sphinx -e sphinx:main -- --helpUsing Entry Points
Projects specifying a console_scripts entry point in their configuration can build standalone executables for those entry points.
To build a standalone pex-tools-executable.pex binary that runs the pex-tools console script found in all pex version 2.1.35 and newer distributions:
$ pex "pex>=2.1.35" --console-script pex-tools --output-file pex-tools-executable.pexSpecifying A Specific Interpreter
You can also build pex files that use a specific interpreter type:
$ pex "pex>=2.1.35" -c pex-tools --python=pypy -o pex-tools-pypy-executable.pexMost pex options compose well with one another, so the above commands can be mixed and matched, and equivalent short options are available.
For a full list of options, just type pex --help.
Documentation
More documentation about Pex, building .pex files, and how .pex files work is available at https://docs.pex-tool.org.
Development
Pex uses uv with dev-cmd for test and development automation. After you have installed uv, to run the Pex test suite, just run dev-cmd via uv:
$ uv run dev-cmdThe dev-cmd command runner provides many useful options, explained at https://pypi.org/project/dev-cmd/ . Below, we provide some of the most commonly used commands when working on Pex, but the docs are worth acquainting yourself with to better understand how dev-cmd works and how to execute more advanced work flows.
To run a specific command, identify the name of the command you’d like to invoke by running uv run dev-cmd --list, then invoke the command by name like this:
$ uv run dev-cmd formatThat’s a fair bit of typing. An shell alias is recommended, and the standard is uvrc which I’ll use from here on out.
To run MyPy:
$ uvrc typecheckAll of our tests allow passthrough arguments to pytest, which can be helpful to run specific tests:
$ uvrc test-py37-integration -- -k test_reproducible_buildTo run Pex from source, rather than through what is on your PATH, invoke via Python:
$ python -m pex3 maintainers
Metadata
3 maintainers
Release files for pex 2.106.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pex-2.106.1.tar.gz | 5.5 MB | With provenance | Details for pex-2.106.1.tar.gz |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pex-2.106.1-py3.py312-none-any.whl | Python 3, Python 3.12 | none | any | Details for pex-2.106.1-py3.py312-none-any.whl |
| pex-2.106.1-py2.py35.py36.py37.py38.py39.py310.py311-none-any.whl | Python 3.8, Python 3.6, Python 3.11, Python 3.10, Python 3.9, Python 3.5, Python 3.7, Python 2 | none | any | Details for pex-2.106.1-py2.py35.py36.py37.py38.py39.py310.py311-none-any.whl |
Total release size: 11.6 MB
Release files / pex-2.106.1.tar.gz
| Download URL | pex-2.106.1.tar.gz |
|---|---|
| Size | 5.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8f7e2d764fa9d961158af29c194a6ab6b2a9fbef2b6fb371ade0d27a1a771d71
|
|
BLAKE2b-256 checksum How to use checksums |
c7972b5c411b5b3e1cfa125a1894067ccea446262ed7d5e9062d255fd7d07c1f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logRelease files / pex-2.106.1-py3.py312-none-any.whl
| Download URL | pex-2.106.1-py3.py312-none-any.whl |
|---|---|
| Size | 2.0 MB |
| Tags | Python 3 Python 3.12 |
|
SHA-256 checksum How to use checksums |
ba928dc0bbf9dce8039722573d4bf3ff34748c1b7268ec961012d877826ac2ba
|
|
BLAKE2b-256 checksum How to use checksums |
3f81b3faf8c780f4495895f7a1510a9d9b96a7a2d63e6fae873332dfbc8a1647
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logRelease files / pex-2.106.1-py2.py35.py36.py37.py38.py39.py310.py311-none-any.whl
| Download URL | pex-2.106.1-py2.py35.py36.py37.py38.py39.py310.py311-none-any.whl |
|---|---|
| Size | 4.1 MB |
| Tags | Python 2 Python 3.10 Python 3.11 Python 3.5 Python 3.6 Python 3.7 Python 3.8 Python 3.9 |
|
SHA-256 checksum How to use checksums |
a6d5edf8dc5d95f0031b05c6566e8369a20036fee1911d6f0b272724bed03121
|
|
BLAKE2b-256 checksum How to use checksums |
90658a6025e0c7fb5a7b8b7eca4c4df5c488ecce4792ede49925a16db858bd22
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logSecurity for pex 2.106.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 3 files in this release have been uploaded with provenance metadata.
Attestation for pex-2.106.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
