pex 2.56.0 #2904
pex 2.56.0
#2904
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
2.56.0
This release adds support for scoping
--indexand--find-linksrepos to only be used to resolvecertain projects, environments or a combination of the two. For example, to use the piwheels index
but restrict its use to resolves targeting armv7l machines, you can now say:
--index piwheels=https://www.piwheels.org/simple --source piwheels=platform_machine == 'armv7l'.See the
--helpoutput for--indexand--find-linksfor more syntax details.Additionally,
--style universallocks have been made aware of top-level inputs that can split thelock resolve and such resolves are pre-split and performed in parallel to allow locking for multiple
non-overlapping universes at once. Splits can be caused by some scoped repos setups as well locks
with multiple differing top-level requirements for the same project. For example, the following will
create a universal lock with two locked resolves, one locking cowsay 5.0 for Python 2 and one
locking cowsay 6.0 for Python 3:
An important use case for this new set of features is creating a universal lock for PyTorch for
CUDA enabled Linux and Mac by adding the appropriate pytorch index appropriately scoped.
For example, this lock will contain two locked resolves, one for Mac sourced purely from PyPI and
one for CUDA 12.9 enabled Linux partially sourced from the PyTorch index for CUDA 12.9:
--indexand--find-links. (Support scopes for--indexand--find-links. #2903)This discussion was created from the release pex 2.56.0.
Beta Was this translation helpful? Give feedback.
All reactions