The PEX packaging toolchain.
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.
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.
To install pex, simply
$ pip install pex
You can also build pex in a git clone using tox:
$ tox -e py27-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.
Launch an interpreter with requests, flask and psutil in the environment:
$ pex requests flask 'psutil>2,<3'
Or instead freeze your current virtualenv via requirements.txt and execute it anywhere:
$ pex -r <(pip freeze) -o my_virtualenv.pex $ deactivate $ ./my_virtualenv.pex
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
Build a standalone pex binary into pex.pex using the pex console_scripts entry point:
$ pex pex -c pex -o pex.pex
You can also build pex files that use a specific interpreter type:
$ pex pex -c pex --python=pypy -o pypy-pex.pex
Most pex options compose well with one another, so the above commands can be mixed and matched. 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 =
pexcommands = pex . -o dist/app.pex
Then tox -e package will produce a relocateable copy of your application that you can copy to staging or production environments.
More documentation about pex, building .pex files, and how .pex files work is available at https://pex.readthedocs.io.
pex uses tox for test and development automation. To run the test suite, just invoke tox:
If you don’t have tox, you can generate a pex of tox:
$ pex tox -c tox -o ~/bin/tox
To contribute, follow these instructions: http://pantsbuild.org/howto_contribute.html
This release follows-up on 1.2.0 fixing bugs in the pre-release resolving code paths.
Fix CacheControl import. (#357) #357
This release is a quick fix for a bootstrapping bug that inadvertently went out in 1.2.0 (Issue #354).
This release changes pex requirement resolution behavior. Only stable requirements are resolved by default now. The previous behavior that included pre-releases can be retained by passing –pre on the pex command line or passing allow_prereleases=True via the API.
Add dummy flush method for clean interpreter exit with python3.6 (#343) #343
Make PEX_PATH unify pex sources, as well as requirements. (#329) #329
Repair passing of stdio kwargs to PEX.run(). (#288) #288
This release is a quick fix for a regression that inadvertently went out in 1.1.5 (Issue #243).
This release is a quick fix for a regression that inadvertently went out in 1.1.3 (Issue #216).
Add a test for the regression in FixedEggMetadata._zipinfo_name and revert the breaking commit. Fixes #216
This release includes an initial body of work towards Windows support, ABI tag support for CPython 2.x and a fix for version number normalization.
Bug fix: PEX_PROFILE_FILENAME and PEX_PROFILE_SORT were not respected. #154.
Adds the bdist_pex command to setuptools. #99.
Bug fix: We did not normalize package names in ResolvableSet, so it was possible to depend on sphinx and Sphinx-1.4a0.tar.gz and get two versions build and included into the pex. #147.
Adds a pex-identifying User-Agent. #101.
Bug fix: Accommodate OSX Python python binaries. Previously the OSX python distributions shipped with OSX, XCode and available via https://www.python.org/downloads/ could fail to be detected using the PythonInterpreter class. Fixes #144.
Bug fix: PEX_SCRIPT failed when the script was from a not-zip-safe egg. Original PR #139.
Bug fix: sys.exit called without arguments would cause None to be printed on stderr since pex 1.0.1. #143.
Bug fix: PEX-INFO values were overridden by environment Variables with default values that were not explicitly set in the environment. Fixes #135.
Bug fix: Since 69649c1 we have been unpatching the side-effects of sys.modules after PEX.execute. This takes all modules imported during the PEX lifecycle and sets all their attributes to None. Unfortunately, sys.excepthook, atexit and __del__ may still try to operate using these tainted modules, causing exceptions on interpreter teardown. This reverts just the sys unpatching so that the abovementioned teardown hooks behave more predictably. Fixes #141.
Allow PEXBuilder to optionally copy files into the PEX environment instead of hard-linking them.
Allow PEXBuilder to optionally skip precompilation of .py files into .pyc files.
Bug fix: PEXBuilder did not respect the target interpreter when compiling source to bytecode. Fixes #127.
Bug fix: Fix complex resolutions when using a cache. Fixes: #120.
The 1.0.0 release of pex introduces a few breaking changes: pex -r now takes requirements.txt files instead of requirement specs, pex -s has now been removed since source specs are accepted as arguments, and pex -p has been removed in favor of its alias pex -o.
The pex command line interface now adheres to semver insofar as backwards incompatible CLI changes will invoke a major version change. Any backwards incompatible changes to the PEX environment variable semantics will also result in a major version change. The pex API adheres to semver insofar as backwards incompatible API changes will invoke minor version changes.
For users of the PEX API, it is recommended to add minor version ranges, e.g. pex>=1.0,<1.1. For users of the PEX CLI, major version ranges such as pex>=1,<2 should be sufficient.
BREAKING CHANGE: Removes the -s option in favor of specifying directories directly as arguments to the pex command line.
BREAKING CHANGE: pex -r now takes requirements.txt filenames and not requirement specs. Requirement specs are now passed as arguments to the pex tool. Use -- to escape command line arguments passed to interpreters spawned by pex. Implements #5.
Adds a number of flag aliases to be more compatible with pip command lines: --no-index, -f, --find-links, --index-url, --no-use-wheel. Removes -p in favor of -o exclusively.
Adds --python-shebang option to the pex tool in order to set the #! shebang to an exact path. #53.
Adds support for PEX_PYTHON environment variable which will cause the pex file to reinvoke itself using the interpreter specified, e.g. PEX_PYTHON=python3.4 or PEX_PYTHON=/exact/path/to/interpreter. #27.
Adds support for PEX_PATH environment variable which allows merging of PEX environments at runtime. This can be used to inject plugins or entry_points or modules from one PEX into another without explicitly building them together. #30.
Consolidates documentation of PEX_ environment variables and adds the --help-variables option to the pex client. Partially addresses #13.
Adds helper method to dump a package subdirectory onto disk from within a zipped PEX file. This can be useful for applications that know they’re running within a PEX and would prefer some static assets dumped to disk instead of running as an unzipped PEX file. #12.
Now supports extras for static URLs and installable directories. #65.
Adds -m and --entry-point alias to the existing -e option for entry points in the pex tool to evoke the similarity to python -m.
Adds console script support via -c/--script/--console-script and PEX_SCRIPT. This allows you to reference the named entry point instead of the exact module:name pair. Also supports scripts defined in the scripts section of setup.py. #59.
Adds more debugging information when encountering unresolvable requirements. #79.
Bug fix: PEX_COVERAGE and PEX_PROFILE did not function correctly when SystemExit was raised. Fixes #81.
Bug fix: Fixes caching in the PEX tool since we don’t cache the source distributions of installable directories. #24.
This is the last release before the 1.0.0 development branch is started.
Adds option groups to the pex tool to make the help output slightly more readable.
Bug fix: Make pip install pex work better by removing extras_requires on the console_script entry point. Fixes #48
New feature: Adds an interpreter cache to the pex tool. If the user does not explicitly disable the wheel feature and attempts to build a pex with wheels but does not have the wheel package installed, pex will download it in order to make the feature work. Implements #47 in order to fix #48
Bug fix: Fixup string formatting in pex/bin/pex.py to support Python 2.6 Pull Request #40
Performance improvement: Speed up the best-case scenario of dependency resolution. RB #1685
Bug fix: Change from uuid4().get_hex() to uuid4().hex to maintain Python3 compatibility of pex.common. Pull Request #39
Bug fix: Actually cache the results of translation. Previously bdist translations would be created in a temporary directory even if a cache location was specified. RB #1666
Bug fix: Support all potential abi tag permutations when determining platform compatibility. Pull Request #33
Performance improvement: Don’t always write packages to disk if they’ve already been cached. This can significantly speed up launching PEX files with a large number of non-zip-safe dependencies. RB #1642
Bug fix: Allow pex 0.8.x to parse pex files produced by earlier versions of pex and twitter.common.python.
Pin pex to setuptools prior to 9.x until we have a chance to make changes related to PEP440 and the change of pkg_resources.py to a package.
Bug fix: Fix issue where it’d be possible to os.path.getmtime on a remote Link object Issue #29
API change: Decouple translation from package iteration. This removes the Obtainer construct entirely, which likely means if you’re using PEX as a library, you will need to change your code if you were doing anything nontrivial. This adds a couple new options to resolve but simplifies the story around how to cache packages. RB #785
Refactor http handling in pex to allow for alternate http implementations. Adds support for requests, improving both performance and security. For more information, read the commit notes at 91c7f32. RB #778
Improvements to API documentation throughout.
Renamed Tracer to TraceLogger to prevent nondeterministic isort ordering.
Refactor tox.ini to increase the number of environment combinations and improve coverage.
Adds HTTP retry support for the RequestsContext. RB #1303
Make pex –version correct. Issue #19
Bug fix: Fix over-aggressive sys.modules scrubbing for namespace packages. Under certain circumstances, namespace packages in site-packages could conflict with packages within a PEX, causing them to fail importing. RB #1378
Bug fix: Replace uses of os.unsetenv(...) with del os.environ[...] Pull Request #11
Bug fix: Scrub sys.path and sys.modules based upon both supplied path and realpath of files and directories. Newer versions of virtualenv on Linux symlink site-packages which caused those packages to not be removed from sys.path correctly. Issue #21
Bug fix: The pex -s option was not correctly pulling in transitive dependencies. Issue #22
Bug fix: Adds content method to HTTP contexts that does HTML content decoding, fixing an encoding issue only experienced when using Python 3. Issue #10
Rename twitter.common.python to pex and split out from the twitter/commons repo.
Change the interpretation of -i (and of PyPIFetcher’s pypi_base) to match pip’s -i. This is useful for compatibility with devpi.
Ensures that .egg/.whl distributions on disk have their mtime updated even though we no longer overwrite them. This gives them a new time lease against their ttl.
Without this change, once a distribution aged past the ttl it would never be used again, and builds would re-create the same distributions in tmpdirs over and over again.
Fixes an issue where SourceTranslator would overwrite .egg/.whl distributions already on disk. Instead it should always check to see if a copy already exists and reuse if there.
This ordinarily should not be a problem but the zipimporter caches metadata by filename instead of stat/sha, so if the underlying contents changed a runtime error would be thrown due to seemingly corrupt zip file offsets. RB #684
Adds -i/--index option to the pex tool.
Adds twitter.common.python.pex_bootstrap bootstrap_pex_env function in order to initialize a PEX environment from within a python interpreter. (Patch contributed by @kwlzn)
Adds stdin=,stdout=,stderr= keyword parameters to the PEX.run function. (Patch from @benjy)
The crawler now defaults to not follow links for security reasons. (Before the default behavior was to implicitly --follow-links for all requirements.) RB #293
Improves scrubbing of site-packages from PEX environments. RB #289
0.5.1 - 0.5.4
Adds twitter.common.python.finders which are additional finders for setuptools including: - find eggs within a .zip - find wheels within a directory - find wheels within a .zip RB #86
Adds a new Package abstraction by refactoring Link into Link and Package. RB #92
Adds support for PEP425 tagging necessary for wheel support. RB #87
Improves python environment isolation by correctly scrubbing namespace packages injected into module __path__ attributes by nspkg pth files. RB #116
Adds twitter.common.python.resolver resolve method that handles transitive dependency resolution better. This means that if the requirement futures==2.1.2 and an unqualified futures>=2 is pulled in transitively, our resolver will correctly resolve futures 2.1.2 instead of reporting a VersionConflict if any version newer than 2.1.2 is available. RB #129
Factors all twitter.common.python test helpers into twitter.common.python.testing RB #91
Bug fix: Fix OrderedSet atexit exceptions RB #147
Bug fix: Fix cross-device symlinking (patch from @benjy)
Bug fix: Raise a RuntimeError if we fail to write pkg_resources into a .pex RB #115
Upgrade to setuptools>=1
twitter.common.python is no longer a namespace package
Kill the egg distiller. We now delegate .egg generation to bdist_egg. RB #55
Plumb through the --zip-safe, --always-write-cache, --ignore-errors and --inherit-path flags to the pex tool.
Delete the unused PythonDirWrapper code.
Split PEXEnvironment resolution into twitter.common.python.environment and deconflate WorkingSet/Environment state.
Removes the monkeypatched zipimporter in favor of keeping all eggs unzipped within PEX files. Refactors the PEX dependency cache in util.py
Adds interpreter detection for Jython and PyPy.
Dependency translation errors should be made uniform. (Patch from @johnsirois)
Adds PEX_PROFILE_ENTRIES to limit the number of entries reported when PEX_PROFILE is enabled. (Patch from @rgs_)
Bug fix: Several fixes to error handling in twitter.common.python.http (From Marc Abramowitz)
Bug fix: PEX should not always assume that $PATH was available. (Patch from @jamesbroadhead)
Bug fix: Filename should be part of the .pex cache key or else multiple identical versions will incorrectly resolve (Patch from @tc)
Bug fix: Executed entry points shouldn’t be forced to run in an environment with __future__ imports enabled. (Patch from @lawson_patrick)
Bug fix: Detect versionless egg links and fail fast. (Patch from @johnsirois.)
Bug fix: Handle setuptools>=2.1 correctly in the zipimport monkeypatch (Patch from @johnsirois.)
Bug fix: Fix handling of Fetchers with file:// urls.
Adds the pex tool as a standalone tool.
Bug fix: Bootstrapped twitter.common.python should declare twitter.common as a namespace package.
Make twitter.common.python fully standalone by consolidating external dependencies within twitter.common.python.common.
Initial published version of twitter.common.python.
Release history Release notifications | RSS feed
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.