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 tox:
$ tox -e 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.
Integrating pex into your workflow
If you use tox (and you should!), a simple way to integrate pex into your workflow is to add a packaging test environment to your tox.ini:
[testenv:package]
deps = pex
commands = pex . -o dist/app.pexThen tox -e package will produce a relocatable copy of your application that you can copy to staging or production environments.
Documentation
More documentation about Pex, building .pex files, and how .pex files work is available at https://docs.pex-tool.org.
Development
Pex uses tox for test and development automation. To run the test suite, just invoke tox:
$ toxIf you don’t have tox, you can generate a pex of tox:
$ pex tox -c tox -o ~/bin/toxTox provides many useful commands and options, explained at https://tox.wiki/en/latest/ . Below, we provide some of the most commonly used commands used when working on Pex, but the docs are worth acquainting yourself with to better understand how Tox works and how to do more advanced commands.
To run a specific environment, identify the name of the environment you’d like to invoke by running tox --listenvs-all, then invoke like this:
$ tox -e fmtTo run MyPy:
$ tox -e checkAll of our tox test environments allow passthrough arguments, which can be helpful to run specific tests:
$ tox -e 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.33.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pex-2.33.4.tar.gz | 4.7 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pex-2.33.4-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 8.4 MB
Release files / pex-2.33.4.tar.gz
| Download URL | pex-2.33.4.tar.gz |
|---|---|
| Size | 4.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ed1c80e2e0f3b075a42288bae79fe22dad517f5b5de11fbc118188e968313add
|
|
BLAKE2b-256 checksum How to use checksums |
caea85c749a5766881aa97e7c16ed22edeaf092ed0e86c3145f8ed0372f402c8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Mar 13, 2025.
Transparency logRelease files / pex-2.33.4-py2.py3-none-any.whl
| Download URL | pex-2.33.4-py2.py3-none-any.whl |
|---|---|
| Size | 3.8 MB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
74adabf5dbe24b47b10b1fdca9d814338339d76e5d536e3f68c18af773f90512
|
|
BLAKE2b-256 checksum How to use checksums |
2166be866dc522514830272e128aae0fec2a0a5e995ce75baa68acf248d8eed0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Mar 13, 2025.
Transparency log
