pex 2.4.0 #2429
pex 2.4.0
#2429
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
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 PEXvia Python from the command line like
python -u my.pex
or via ashebang with embedded Python arguments like
#!/usr/bin/python -u
.In addition, PEXes can now be built with
--inject-python-args
similarto the existing
--inject-args
but sealing in arguments to pass toPython 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 itsintroduction 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 containingeither 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 outsidePex, a new
--format
option ofpip-no-hashes
is introduced for theadventurous.
--exclude
. (Fix--exclude
. #2409)pex3 lock export
handling of exotic reqs. (Fixpex3 lock export
handling of exotic reqs. #2423)Beta Was this translation helpful? Give feedback.
All reactions