NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI, #1847 most downloaded on PyPI
The PEX packaging toolchain.
Latest stable
2.107.1
Last release 16 days ago
06 Nov 2026
Ships on a steady schedule
a new release about every 9 days
Nearly every release is documented
notes for 60 of the last 60 stable releases
2 versions withdrawn
withdrawn after publishing
13 years old
522 releases · first in 2014
Drag across the ruler to compare, or tap a release to open it.
This release adds support for --venv-system-site-packages when creating a --venv PEX and --system-site-packages when creating a venv using the pex-too
This release adds support for --venv-system-site-packages when
creating a --venv PEX and --system-site-packages when creating a
venv using the pex-tools / PEX_TOOLS=1 venv command or when using
the pex3 venv create command. Although this breaks PEX hermeticity, it
can be the most efficient way to ship partial PEX venvs created with
--excludes to machines that have the excluded dependencies already
installed in the site packages of a compatible system interpreter.
--system-site-packages when creating venvs. (#2500)This release enhances the REPL your PEX drops into when it either doesn't have an entry point or you force interpreter mode with the PEX_INTERPRETER e
This release enhances the REPL your PEX drops into when it either
doesn't have an entry point or you force interpreter mode with the
PEX_INTERPRETER environment variable. There is now clear indication
you are running in a PEX hermetic environment and a pex command
added to the REPL that you can use to find out more details about the
current PEX environment.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
This release fixes --inject-env when used in combination with a --scie-busybox so that the injected environment variable can be overridden at runtime
This release fixes --inject-env when used in combination with a
--scie-busybox so that the injected environment variable can be
overridden at runtime like it can form a traditional PEX.
In addition, running a PEX with the Python interpreter -i flag or
PYTHONINSPECT=x in the environment causes the PEX to enter the
Python REPL after evaluating the entry point, if any.
--inject-env overrides for --scie-busybox. (#2490)-i / PYTHONINSPECT=x. (#2491)This release brings support for creating PEX scies for PEXes targeting PyPy. In addition, for PEX scies targeting CPython, you can now specify --scie-
This release brings support for creating PEX scies for PEXes targeting
PyPy. In addition, for PEX scies targeting CPython, you can now
specify --scie-pbs-stripped to select a stripped version of the
Python Standalone Builds CPython distribution embedded in your
scie to save transfer bandwidth and disk space at the cost of losing
Python debug symbols.
Finally, support is added for --scie-busybox to turn your PEX into a
multi-entrypoint BusyBox-like scie. This support is
documented in depth at https://docs.pex-tool.org/scie.html
--scie for PyPy & support stripped CPython. (#2488)--scie-busybox. (#2468)This release fixes the --scie option to support building a Pex PEX scie with something like pex pex -c pex --venv --scie eager -o pex. Previously, due
This release fixes the --scie option to support building a Pex PEX
scie with something like pex pex -c pex --venv --scie eager -o pex.
Previously, due to the output filename of pex colliding with fixed
internal scie lift manifest file names, this would fail.
This release improves error message detail when there are failures in Pex sub-processes. In particular, errors that occur in pip download when buildin
This release improves error message detail when there are failures in
Pex sub-processes. In particular, errors that occur in pip download
when building a PEX or creating a lock file now give more clear
indication of what went wrong.
Additionally, this release adds support for --pip-version 24.2.
--pip-version 24.2. (#2481)This refresh addresses at least CVE-2023-37920 and was spearheaded by a contribution from Nash Kaminski in https://github.com/pex-tool/pip/pull/12. Th…
This release refreshes the root CA cert bundle used by
--pip-version vendored (which is the default Pip Pex uses for
Python <3.12) from certifi 2019.9.11's cacert.pem to
certifi 2024.7.4's
cacert.pem. This refresh addresses at least CVE-2023-37920 and was spearheaded by
a contribution from Nash Kaminski in
https://github.com/pex-tool/pip/pull/12. Thank you, Nash!
This release adds support for passing --site-packages-copies to both pex3 venv create ... and PEX_TOOLS=1 ./my.pex venv .... This is similar to pex --
This release adds support for passing --site-packages-copies to both
pex3 venv create ... and PEX_TOOLS=1 ./my.pex venv .... This is
similar to pex --venv --venv-site-packages-copies ... except that
instead of preferring hard links, a copy is always performed. This is
useful to disassociate venvs you create using Pex from Pex's underlying
PEX_ROOT cache.
This release also adds partial support for statically linked CPython. If
the statically linked CPython is <3.12, the default Pip (
--pip-version vendored) used by Pex will work. All newer Pips will not
though, until Pip 24.2 is released with the fix in
https://github.com/pypa/pip/pull/12716 and Pex releases with support for
--pip-version 24.2.
--site-packages-copies for external venvs. (#2470)This release adds support for creating native PEX executables that contain their own hermetic CPython interpreter courtesy of Python Standalone Builds
This release adds support for creating native PEX executables that contain their own hermetic CPython interpreter courtesy of Python Standalone Builds and the Science project.
You can now specify --scie {eager,lazy} when building a PEX file and
one or more native executable PEX scies will be produced (one for each
platform the PEX supports). These PEX scies are single file
executables that look and behave like traditional PEXes, but unlike
PEXes they can run on a machine with no Python interpreter available.
--scie option to produce native PEX exes. (#2466)This release adds support for creating native PEX executables that contain their own hermetic CPython interpreter courtesy of Python Standalone Builds and the Science project.
You can now specify --scie {eager,lazy} when building a PEX file and
one or more native executable PEX scies will be produced (one for each
platform the PEX supports). These PEX scies are single file
executables that look and behave like traditional PEXes, but unlike
PEXes they can run on a machine with no Python interpreter available.
--scie option to produce native PEX exes. (#2466)This release fixes a long-standing bug in Pex parsing of editable requirements. This bug caused PEXes containing local editable project requirements t
This release fixes a long-standing bug in Pex parsing of editable requirements. This bug caused PEXes containing local editable project requirements to fail to import those local editable projects despite the fact the PEX itself contained them.
This release adds support for injecting requirements into the isolated Pip PEXes Pex uses to resolve distributions. The motivating use case for this i
This release adds support for injecting requirements into the isolated
Pip PEXes Pex uses to resolve distributions. The motivating use case
for this is to use the feature Pip 23.1 introduced for forcing
--keyring-provider import.
Pex already supported using a combination of the following to force non-interactive use of the keyring:
keyring script installation that was on the PATH--pip-version 23.1 or newer.--use-pip-config to pass --keyring-provider subprocess
to Pip.You could not force --keyring-provider import though, since the Pips
Pex uses are themselves hermetic PEXes without access to extra
installed keyring requirements elsewhere on the system. With
--extra-pip-requirement you can now do this with the primary benefit
over --keyring-provider subprocess being that you do not need to add
the username to index URLs. This is ultimately because the keyring CLI
requires username whereas the API does not; but see
https://pip.pypa.io/en/stable/topics/authentication/#keyring-support for
more information.
--extra-pip-requirement. (#2461)This release adds support for Pip 24.1.2.
This release adds support for Pip 24.1.2.
--pip-version 24.1.2. (#2459)This release fixes the bdist_pex distutils command to use the --project option introduced by #2455 in the 2.8.0 release. This change produces the same
This release fixes the bdist_pex distutils command to use the
--project option introduced by #2455 in the 2.8.0 release. This
change produces the same results for existing invocations of
python setup.py bdist_pex but allows new uses passing locked project
requirements (either hashed requirement files or Pex lock files) via
--pex-args.
bdist_pex to use --project. (#2457)This release adds a new --override option to resolves that ultimately use an --index or --find-links. This allows you to override transitive dependenc
This release adds a new --override option to resolves that ultimately
use an --index or --find-links. This allows you to override
transitive dependencies when you have determined they are too narrow and
that expanding their range is safe to do. The new --overrides and the
existing --excludes can now also be specified when creating or syncing
a lock file to seal these dependency modifications into the lock.
This release also adds a new --project option to pex and
pex3 lock {create,sync} that improves the ergonomics of locking a
local Python project and then creating PEX executables for that project
using its locked requirements.
In addition, this release fixes the bdist_pex distutils command that
ships with Pex to work when run under tox and Python 3.12 by improving
Pex venv creation robustness when creating venvs that include Pip.
--override. (#2431)--project locking and PEX building. (#2455)This release adds support for Pip 24.1.1.
This release adds support for Pip 24.1.1.
--pip-version 24.1.1. (#2451)There are no changes to Pex code or released artifacts over 2.6.1 or 2.6.2, just a further fix to the GitHub Releases release process which
There are no changes to Pex code or released artifacts over 2.6.1 or 2.6.2, just a further fix to the GitHub Releases release process which #2442 broke and #2444 only partially fixed.
> Although 2.6.2 successfully released to [PyPI](
[!NOTE] Although 2.6.2 successfully released to PyPI, it failed to release to GitHub Releases (neither the Pex PEX nor the pex.pdf were published.) You can use Pex 2.6.3 instead which has no Pex code changes over this release.
There are no changes to Pex code or released artifacts over 2.6.1, just a fix to the GitHub Releases release process which #2442 broke.
> Although 2.6.1 successfully released to [PyPI](
[!NOTE] Although 2.6.1 successfully released to PyPI, it failed to release to GitHub Releases (neither the Pex PEX nor the pex.pdf were published.) You can use Pex 2.6.3 instead which has no Pex code changes over this release.
This release improves error messages when attempting to read invalid metadata from distributions such that the problematic distribution is always identified.
This release adds support for PEP-723 script metadata in --exes. For such a script with metadata describing its dependencies or Python version require
This release adds support for PEP-723 script metadata in --exes. For such
a script with metadata describing its dependencies or Python version
requirements, running the script is as simple as
pex --exe <script> -- <script args> and building a PEX encapsulating
it as simple as pex --exe <script> --output <PEX file>.
--exe. (#2436)This release brings support for Python 3.13 and --pip-version 24.1, which is the first Pip version to support it.
This release brings support for Python 3.13 and --pip-version 24.1,
which is the first Pip version to support it.
--pip-version 24.1 and Python 3.13. (#2435)This release fixes pex --only-binary X --lock ... to work with lock files also created with --only-binary X. The known case here is a --style universa
This release fixes pex --only-binary X --lock ... to work with lock
files also created with --only-binary X. The known case here is a
--style universal lock created with --only-binary X to achieve a
partially wheel-only universal lock.
pex --only-binary X --lock .... (#2433)This release brings new support for preserving arguments passed to the Python interpreter (like -u or -W ignore) either via running a PEX via Python f
This release brings new support for preserving arguments passed to the
Python interpreter (like -u or -W ignore) either via running a PEX
via Python from the command line like python -u my.pex or via a
shebang with embedded Python arguments like #!/usr/bin/python -u.
In addition, PEXes can now be built with --inject-python-args similar
to the existing --inject-args but sealing in arguments to pass to
Python instead. When both explicitly passed Python interpreter arguments
and injected Python interpreter arguments are specified, the injected
arguments appear first on the synthesized command line and the
explicitly passed arguments appear last so that the explicit arguments
can trump (which is how Python handles this).
Several bugs existing in the --exclude implementation since its
introduction are now fixed and the feature is greatly improved to act on
excludes eagerly, never traversing them in the resolve process; thus
avoiding downloads associated with them as well as potentially failing
metadata extraction & wheel builds for ill-behaved sdists.
Finally, a bug was fixed in pex3 lock export for lock files containing
either locked VCS requirements or locked local project directories.
Previously, these were exported with a <project name>==<version>
requirement, which lost fidelity with the input requirement. Now they
are exported with their original requirement form. Further, since the
--hash of these styles of locked requirement are unuseable outside
Pex, a new --format option of pip-no-hashes is introduced for the
adventurous.
--exclude. (#2409)pex3 lock export handling of exotic reqs. (#2423)This release fixes pex3 lock create support for --pip-versions 23.3.1 and newer. Previously, when locking using indexes that serve artifacts via re-di
This release fixes pex3 lock create support for --pip-versions
23.3.1 and newer. Previously, when locking using indexes that serve
artifacts via re-directs, the resulting lock file would contain the
final re-directed URL instead of the originating index artifact URL.
This could lead to issues when the indexes re-direction scheme changed
or else if authentication parameters in the original index URL were
stripped in the Pip logs.
pip>=23.3. (#2421)This release fixes a regression for users of gevent monkey patching. The fix in #2356 released in Pex 2.1.163 lead to these users receiving spurious w
This release fixes a regression for users of gevent monkey patching. The fix in #2356 released in Pex 2.1.163 lead to these users receiving spurious warnings from the gevent monkey patch system about ssl being patched too late.
pex.fetcher. (#2417)This release fixes Pex to respect lock file interpreter constraints and target systems when downloading artifacts.
This release fixes Pex to respect lock file interpreter constraints and target systems when downloading artifacts.
This release introduces pex3 lock sync as a higher-level tool that can be used to create and maintain a lock as opposed to using a combination of pex3
This release introduces pex3 lock sync as a higher-level tool that
can be used to create and maintain a lock as opposed to using a
combination of pex3 lock create and pex3 lock update. When there is
no existing lock file, pex3 lock sync --lock lock.json ... is
equivalent to pex3 lock create --output lock.json ..., it creates a
new lock. On subsequent uses however,
pex3 lock sync --lock lock.json ... updates the lock file minimally to
meet any changed requirements or other changed lock settings.
This release also fixes pex --no-build --lock ... to work with lock
files also created with --no-build. The known case here is a
--style universal lock created with --no-build to achieve a
wheel-only universal lock.
This release includes a fix to clarify the conditions under which
--requierements-pex can be used to combine the third party
dependencies from a pre-built PEX into a new PEX; namely, that the PEXes
must use the same value for the --pre-install-wheels option.
Finally, this release fixes pex3 venv to handle venvs created by
Virtualenv on systems that distinguish purelib and platlib
site-packages directories. Red Hat distributions are a notable example
of this.
--requirements-pex. (#2392)pex --no-build --lock .... (#2390)This release fixes pex3 lock create to handle .tar.bz2 and .tgz sdists in addition to the officially sanctioned .tar.gz and (less officially so) .zip
This release fixes pex3 lock create to handle .tar.bz2 and .tgz
sdists in addition to the officially sanctioned .tar.gz and (less
officially so) .zip sdists.
.tar.bz2 & .tgz sdists when locking. (#2380)This release trims down the size of the Pex wheel on PyPI and the released Pex PEX by about 20KB by consolidating image resources.
This release trims down the size of the Pex wheel on PyPI and the released Pex PEX by about 20KB by consolidating image resources.
This release also fixes the release process to remove a window of time when several links would be dead on at https://docs.pex-tool.org that pointed to release artifacts that were not yet fully deployed.
This release adds tools to interact with Pex's new embedded offline documentation. You can browse those docs with pex --docs or, more flexibly, with p
This release adds tools to interact with Pex's new embedded offline
documentation. You can browse those docs with pex --docs or, more
flexibly, with pex3 docs. See pex3 docs --help for all the options
available.
This release also returns to SemVer versioning practices. Simply, you can expect 3 things from Pex version numbers:
You can expect the minor version to get pretty big going forward!
pex --docs and several pex3 docs options. (#2365)This release moves Pex documentation from https://pex.readthedocs.io to https://docs.pex-tool.org. While legacy versioned docs will remain available a
This release moves Pex documentation from https://pex.readthedocs.io to
https://docs.pex-tool.org. While legacy versioned docs will remain
available at RTD in perpetuity, going forward only the latest Pex
release docs will be available online at the https://docs.pex-tool.org
site. If you want to see the Pex docs for the version you are currently
using, Pex now supports the pex3 docs command which will serve the
docs for your Pex version locally, offline, but with full functionality,
including search.
This release fixes Pex to work in certain OS / SSL environments where it did not previously. In particular, under certain Fedora distributions using c
This release fixes Pex to work in certain OS / SSL environments where it did not previously. In particular, under certain Fedora distributions using certain Python Build Standalone interpreters.
This release adds support for --pip-version 24.0 as well as fixing a bug in URL encoding for artifacts in lock files. Notably, torch's use of local ve
This release adds support for --pip-version 24.0 as well as fixing a
bug in URL encoding for artifacts in lock files. Notably, torch's use of
local version identifiers (+cpu) combined with their find links page
at https://download.pytorch.org/whl/torch_stable.html would lead to
pex3 lock create errors.
This release adds support for --only-wheel and --only-build to allow finer control over which distribution artifacts are resolved when building a PEX
This release adds support for --only-wheel <project name> and
--only-build <project name> to allow finer control over which
distribution artifacts are resolved when building a PEX or creating or
updating a lock file. These options correspond to Pip's --only-binary
and --no-binary options with project name arguments.
--{no,only}-binary. (#2346)This release adds the ability for pex3 lock update to replace requirements in a lock or delete them from the lock using -R / --replace-project and -d
This release adds the ability for pex3 lock update to replace
requirements in a lock or delete them from the lock using
-R / --replace-project and -d / --delete-project, respectively.
This release brings a fix for leaks of Pex's vendored attrs onto the sys.path of PEXes during boot in common usage scenarios.
This release brings a fix for leaks of Pex's vendored attrs onto the
sys.path of PEXes during boot in common usage scenarios.
sys.path leak. (#2328)This release adds support for tab completion to all PEX repls running under Pythons with the readline module available. This tab completion support is
This release adds support for tab completion to all PEX repls running
under Pythons with the readline module available. This tab completion
support is on-par with newer Python REPL out of the box tab completion
support.
This release fixes a bug in pex3 lock update for updates that leave projects unchanged whose primary artifact is an sdist.
This release fixes a bug in pex3 lock update for updates that leave
projects unchanged whose primary artifact is an sdist.
This release optimizes wheel install overhead for warm caches. Notably, this speeds up warm boot for PEXes containing large distributions like PyTorch
This release optimizes wheel install overhead for warm caches. Notably, this speeds up warm boot for PEXes containing large distributions like PyTorch as well as creating venvs from them.
This release brings support for --pip-version 23.3.2 along with optimizations that reduce built PEX size for both --include-tools and --venv PEXes (wh
This release brings support for --pip-version 23.3.2 along with
optimizations that reduce built PEX size for both --include-tools and
--venv PEXes (which includes the Pex PEX) as well as reduce PEX build
time for --pre-install-wheels PEXes (the default) and PEX cold first
boot time for --no-pre-install-wheels PEXes that use more than one
parallel install job.
Pip.spawn_install_wheel & optimize. (#2305)This release brings three new features:
This release brings three new features:
--python-shebang, an appropriate shebang is chosen correctly in
more cases than previously and a warning is emitted when the shebang
chosen cannot be guaranteed to be correct. The common case this
helps select the appropriate shebang for is PEXes built using
--platform or --complete-platform.--no-pre-install-wheels to cut down
PEX build times with a tradeoff of roughly 10% greater boot overhead
upon the 1st execution of the PEX file. For PEXes with very large
dependency sets (machine learning provides common cases), the build
time savings can be dramatic.--max-install-jobs at PEX
build time or by setting the PEX_MAX_INSTALL_JOBS environment
variable at runtime.The last two features come with complicated tradeoffs and are turned off
by default as a result. If you think they might help some of your use
cases, there is more detail in the command line help for
--no-pre-install-wheels and --max-install-jobs as well as in the
pex --help-variables output for PEX_MAX_INSTALL_JOBS. You can also
find a detailed performance analysis in #2292 for the extreme cases of
very small and very large PEXes. In the end though, experimenting is
probably your best bet.
This release fixes Pex runtime sys.path scrubbing to do less work and thus avoid errors parsing system installed distributions with bad metadata.
This release fixes Pex runtime sys.path scrubbing to do less work and
thus avoid errors parsing system installed distributions with bad
metadata.
This release fixes the computation of the hash of the code within a PEX when nested within directories, a bug introduced in 2.1.149.
This release fixes the computation of the hash of the code within a PEX when nested within directories, a bug introduced in 2.1.149.
This release brings support for a new --exclude PEX build option that allows eliding selected resolved distributions from the final PEX. This is an ad
This release brings support for a new --exclude <req> PEX build option
that allows eliding selected resolved distributions from the final PEX.
This is an advanced feature that will, in general, lead to broken PEXes
out of the box; so read up on the --exclude command line help to make
sure you understand the consequences.
This release also brings a fix for --inject-env that ensures the
specified environment variables are always injected to the PEX at
runtime regardless of the PEX entry point exercised.
--exclude <req>. (#2281)This release brings support for --pip-version 23.3.1.
This release brings support for --pip-version 23.3.1.
Fix --style universal lock handing of none ABI wheels with a specific Python minor version expressed in their wheel tag. There are not many of these i
Fix --style universal lock handing of none ABI wheels with a
specific Python minor version expressed in their wheel tag. There are
not many of these in the wild, but a user discovered the case of
python-forge 18.6.0 which supplies 1 file on PyPI:
python_forge-18.6.0-py35-none-any.whl.
Add support to the Pex for checking if built PEXes are valid Python zipapps. Currently, Python zipapps must reside in 32 bit zip files due to limitati
Add support to the Pex for checking if built PEXes are valid Python
zipapps. Currently, Python zipapps must reside in 32 bit zip files due
to limitations of the stdlib zipimport module's zipimporter; so this
check amounts to a check that the built PEX zip does not use ZIP64
extensions. The check is controlled with a new
--check {none,warn,error} option, defaulting to warn.
Add support for --use-pip-config to allow the Pip Pex calls to read PIP_* env vars and Pip configuration files. This can be particularly useful for pi
Add support for --use-pip-config to allow the Pip Pex calls to read
PIP_* env vars and Pip configuration files. This can be particularly
useful for picking up custom index configuration (including auth).
This release brings a fix by new contributor @yjabri for the __pex__ import hook that gets it working properly for --venv mode PEXes.
This release brings a fix by new contributor @yjabri for the __pex__
import hook that gets it working properly for --venv mode PEXes.
This release broadens the range of the flit-core build system Pex uses to include 3.x, which is known to work for modern Python versions and Pex's exi
This release broadens the range of the flit-core build system Pex uses
to include 3.x, which is known to work for modern Python versions and
Pex's existing build configuration.
This release fixes Pex to build PEX files with deterministic file order regardless of the operating system / file system the PEX was built on.
This release fixes Pex to build PEX files with deterministic file order regardless of the operating system / file system the PEX was built on.
This release fixes Pex to work by default under eCryptFS home dirs.
This release fixes Pex to work by default under eCryptFS home dirs.
This release fixes Pex to handle Pip backtracking due to sdist build errors when attempting to extract metadata.
This release fixes Pex to handle Pip backtracking due to sdist build errors when attempting to extract metadata.
This release fixes the Pex CLI to work when run from a read-only installation. A prominent example of this comes in certain nix setups.
This release fixes the Pex CLI to work when run from a read-only installation. A prominent example of this comes in certain nix setups.
This release fixes several spurious warnings emitted for Python 3.11 and 3.12 users and fixes a leak of Pex's vendored attrs when using the __pex__ im
This release fixes several spurious warnings emitted for Python 3.11 and
3.12 users and fixes a leak of Pex's vendored attrs when using the
__pex__ import hook.
This release brings support for Python 3.12 and Pip 23.2 which is the minimum required Pip version for Python 3.12. N.B.: Since Pip 23.2 requires Pyth
This release brings support for Python 3.12 and Pip 23.2 which is the minimum required Pip version for Python 3.12. N.B.: Since Pip 23.2 requires Python 3.7 or newer, multiplatform PEX files and locks that support Python 3.12 will not also be able to support Python 2.7, 3.5 or 3.6 even though Pex continues to support those versions generally.
In addition, two new options for adding local project source files to
a pex are added: -P/--package and -M/--module. Importantly, you can
use the options instead of the existing -D/--sources-directory when
you have a project with code at the top level (i.e.: not in a src/
subdirectory for example) intermixed with other files you prefer not to
include in the PEX. See pex --help for more details on using these new
options.
Finally, an internal API is fixed that allows for Lambdex files to
include versions of attrs incompatible with Pex's own vendored version.
pex.pex_bootstrapper.bootstrap_pex_env leak. (#2184)This release brings fixes for two obscure corner cases.
This release brings fixes for two obscure corner cases.
Previously, if you used --venv PEXes in the default symlinked
site-packages mode that contained first party code in a namespace
package shared with 3rd-party dependencies the first party code would
contaminate the Pex installed wheel cache for one of the 3rd-party
dependencies in PEX.
Even more obscure (the only known issue was in Pex's own CI), if you
ran the Pex CLI concurrently using two different --pip-version
arguments, you may have seen spurious Pip HTTP errors that found an
invalid Content-Type: Unknown header.
This release fixes a long standing bug in lock file creation for exotic locking scenarios pulling the same project from multiple artifact sources (any
This release fixes a long standing bug in lock file creation for exotic locking scenarios pulling the same project from multiple artifact sources (any mix of URLs, VCS and local project directories).
This release adds the pex3 lock export-subset command. This is a version of pex3 lock export that also accepts requirements arguments allowing just a
This release adds the pex3 lock export-subset command. This is a
version of pex3 lock export that also accepts requirements arguments
allowing just a subset of the lock satisfying the given requirements to
be exported.
pex3 lock export-subset. (#2145)This release brings support for pex3 venv {inspect,create} for working with venvs directly using Pex. Previously, a PEX built with --include-tools (or
This release brings support for pex3 venv {inspect,create} for
working with venvs directly using Pex. Previously, a PEX built with
--include-tools (or --venv) had the capability of turning itself
into a venv but the new pex3 venv create command can do this for any
PEX file with the addition of a few new features:
pip install --target. This style layout can also be
zipped and prefixed. Additionally it supports --platform and
--complete-platform allowing creation of, for example, an AWS
Lambda (or Lambda Layer) deployment zip on a non-Linux host.Additionally this release adds support for Pip 23.1.1 and 23.1.2.
This release fixes pex3 lock create gathering of sdist metadata for PEP-517 build backends with non-trivial get-requires-for-build-wheel requirements.
This release fixes pex3 lock create gathering of sdist metadata for
PEP-517 build backends with non-trivial get-requires-for-build-wheel
requirements.
One column per quarter.