pex 2.3.0 #2393
pex 2.3.0
#2393
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
2.3.0
This release introduces
pex3 lock sync
as a higher-level tool thatcan be used to create and maintain a lock as opposed to using a
combination of
pex3 lock create
andpex3 lock update
. When there isno existing lock file,
pex3 lock sync --lock lock.json ...
isequivalent to
pex3 lock create --output lock.json ...
, it creates anew lock. On subsequent uses however,
pex3 lock sync --lock lock.json ...
updates the lock file minimally tomeet any changed requirements or other changed lock settings.
This release also fixes
pex --no-build --lock ...
to work with lockfiles also created with
--no-build
. The known case here is a--style universal
lock created with--no-build
to achieve awheel-only universal lock.
This release includes a fix to clarify the conditions under which
--requierements-pex
can be used to combine the third partydependencies 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 byVirtualenv on systems that distinguish
purelib
andplatlib
site-packages directories. Red Hat distributions are a notable example
of this.
--requirements-pex
. (Guard against mismatched--requirements-pex
. #2392)pex --no-build --lock ...
. (Fixpex --no-build --lock ...
. #2390)This discussion was created from the release pex 2.3.0.
Beta Was this translation helpful? Give feedback.
All reactions