Skip to main content

PEX

https://github.com/pex-tool/pex/actions/workflows/ci.yml/badge.svg?branch=main https://img.shields.io/pypi/l/pex.svg https://img.shields.io/pypi/v/pex.svg https://img.shields.io/pypi/pyversions/pex.svg https://img.shields.io/pypi/wheel/pex.svg https://img.shields.io/discord/1205942638763573358

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 pex

You can also build pex in a git clone using uv:

$ uv run dev-cmd package
$ cp dist/pex ~/bin

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

Ephemeral Environments

Run webserver.py in an environment containing flask as a quick way to experiment:

$ pex flask -- webserver.py

Launch Sphinx in an ephemeral pex environment using the Sphinx entry point sphinx:main:

$ pex sphinx -e sphinx:main -- --help

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

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

Most 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-cmd

The 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 format

That’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 typecheck

All of our tests allow passthrough arguments to pytest, which can be helpful to run specific tests:

$ uvrc test-py37-integration -- -k test_reproducible_build

To run Pex from source, rather than through what is on your PATH, invoke via Python:

$ python -m pex

Metadata

Release files for pex 2.105.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pex 2.105.0
File Size Uploaded Provenance
pex-2.105.0.tar.gz 5.5 MB With provenance Details

Built distributions (wheels)

Table of built distributions (wheels) for pex 2.105.0
File Interpreter ABI Platform
pex-2.105.0-py3.py312-none-any.whl Python 3, Python 3.12 none any Details
pex-2.105.0-py2.py35.py36.py37.py38.py39.py310.py311-none-any.whl Python 3.6, Python 2, Python 3.10, Python 3.8, Python 3.11, Python 3.7, Python 3.9, Python 3.5 none any Details

Total release size: 11.5 MB

Release files / pex-2.105.0.tar.gz

Download URL pex-2.105.0.tar.gz
Size 5.5 MB
Tags Source
SHA-256 checksum
How to use checksums
1d24fbe0bc208183f7fefcff1834ae7527f36235f59cc447d29d0d1ab12518ae
BLAKE2b-256 checksum
How to use checksums
f4b26a6e1ab4f1287f74200df106eef6f6fca832b5bb0300c84de52de3bbb4ea
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 Oct 24, 2026.

Transparency log

Release files / pex-2.105.0-py3.py312-none-any.whl

Download URL pex-2.105.0-py3.py312-none-any.whl
Size 1.9 MB
Tags Python 3 Python 3.12
SHA-256 checksum
How to use checksums
256656699103a7852646ec5c3b0e58417ffbc6a62ce2082d9376e0447a2c463d
BLAKE2b-256 checksum
How to use checksums
bbcdb7750d9c09343c8051e605db22be06d0b1495ab447d5676264f1d3db4258
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 Oct 24, 2026.

Transparency log

Release files / pex-2.105.0-py2.py35.py36.py37.py38.py39.py310.py311-none-any.whl

Download URL pex-2.105.0-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
754967f4e0af3328e9400740c282895faa6675b8c4458e9acad403abffa30a57
BLAKE2b-256 checksum
How to use checksums
5cba9e39efe25140428a7e3c3a95709923fe0956c82a75a260cc054ea991fdca
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 Oct 24, 2026.

Transparency log

Security for pex 2.105.0

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.

Select from 3 files

Attestation for pex-2.105.0.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 Oct 24, 2026.

Transparency log

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

Release history Release notifications | RSS feed

This release

2.105.0 This release

3 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page