Releases: pex-tool/pex
pex 2.8.1
2.8.1
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.
- Fix
bdist_pexto use--project. (#2457)
pex 2.8.0
2.8.0
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.
pex 2.7.0
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)