Skip to main content
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

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

pex-2.100.3.tar.gz (5.4 MB view details)

Uploaded Source

Built Distributions

If you're not sure about the file name format, learn more about wheel file names.

pex-2.100.3-py3.py312-none-any.whl (1.9 MB view details)

Uploaded Python 3Python 3.12

pex-2.100.3-py2.py35.py36.py37.py38.py39.py310.py311-none-any.whl (4.1 MB view details)

Uploaded Python 2Python 3.10Python 3.11Python 3.5Python 3.6Python 3.7Python 3.8Python 3.9

File details

Details for the file pex-2.100.3.tar.gz.

File metadata

  • Download URL: pex-2.100.3.tar.gz
  • Upload date:
  • Size: 5.4 MB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for pex-2.100.3.tar.gz
Algorithm Hash digest
SHA256 d3492faf75a199bfb95c84f93d6d59171b6b381f0ebae903c287a08df215ba93
MD5 bb8fa2d196ca47d8bea5cf4373517557
BLAKE2b-256 7748867f272acf8921e678b0057d08a9028bd62ace63f5af102b7c5633949436

See more details on using hashes here.

Provenance

The following attestation bundles were made for pex-2.100.3.tar.gz:

Publisher: release.yml on pex-tool/pex

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file pex-2.100.3-py3.py312-none-any.whl.

File metadata

  • Download URL: pex-2.100.3-py3.py312-none-any.whl
  • Upload date:
  • Size: 1.9 MB
  • Tags: Python 3, Python 3.12
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for pex-2.100.3-py3.py312-none-any.whl
Algorithm Hash digest
SHA256 299f6ed6b1eb9fede312ced3f84623b2dea27e24f46384ca7de6d66e93782ab2
MD5 08ca5eca9c93b3856ef16e137a52c906
BLAKE2b-256 e350d8f724e265ae686eaf9eecc5536021107d8bb2921f30744d73ba67f712d0

See more details on using hashes here.

Provenance

The following attestation bundles were made for pex-2.100.3-py3.py312-none-any.whl:

Publisher: release.yml on pex-tool/pex

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file pex-2.100.3-py2.py35.py36.py37.py38.py39.py310.py311-none-any.whl.

File metadata

File hashes

Hashes for pex-2.100.3-py2.py35.py36.py37.py38.py39.py310.py311-none-any.whl
Algorithm Hash digest
SHA256 0775555ba18814a0b8476a1d4a1cb216e14b7ffa2620b9d87b3bdd3d7a8a54b1
MD5 faf331e802714663657829cf39855828
BLAKE2b-256 ae4c43858e57080dcf4fcced16b0312f2feb4391cb6cc2d9d98169b04474b3f1

See more details on using hashes here.

Provenance

The following attestation bundles were made for pex-2.100.3-py2.py35.py36.py37.py38.py39.py310.py311-none-any.whl:

Publisher: release.yml on pex-tool/pex

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Release history Release notifications | RSS feed

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page