Releases: pex-tool/pex
pex 2.6.3
pex 2.6.0
2.6.0
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>.
- Add support for PEP-723 script metadata to
--exe. (#2436)
pex 2.5.0
pex 2.4.1
pex 2.4.0
2.4.0
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.
pex 2.3.3
2.3.3
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.
- Fix artifact URL recording for
pip>=23.3. (#2421)
pex 2.3.2
pex 2.3.1
pex 2.3.0
2.3.0
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.