pex 2.18.0 #2525
pex 2.18.0
#2525
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
2.18.0
This release adds support for
pex3 cache {dir,info,purge}
forinspecting and managing the Pex cache. Notably, the
pex3 cache purge
command is safe in the face of concurrent PEX runs, waiting for in
flight PEX runs to complete and blocking new runs from starting once the
purge is in progress. N.B.: when using
pex3 cache purge
it is best toinstall Pex with the 'management' extra; e.g.:
pip install pex[management]
. Alternatively, one of the new Pex sciebinary releases can be used.
In order to release a Pex binary that can support the new
pex3
cachemanagement commands first class, a set of enhancements to project
locking and scie generation were added. When using
--project
you cannow specify extras; e.g.:
--project ./the/project-dir[extra1,extra2]
.When creating a Pex scie, you can now better control the output files
using
--scie-only
to ensure no PEX file is emitted and--scie-name-style
to control how the scie target platform name ismixed into the scie output file name. Additionally, you can request one
or more shasum-compatible checksum files be emitted for each scie with
--scie-hash-alg
.On the locking front, an obscure bug locking project releases that
contain artifacts that mis-report their version number via their file
name has been fixed.
Finally, the vendored Pip has had its own vendored CA cert bundle
upgraded from that in certifi 2024.7.4 to that in certifi 2024.8.30.
--scie-only
&--scie-name-style
. (Add--scie-only
&--scie-name-style
. #2523)--project
extras. (Support--project
extras. #2522)--scie-hash-alg
. (Support shasum file gen via--scie-hash-alg
. #2520)pex3 cache {dir,info,purge}
. (Introducepex3 cache {dir,info,purge}
. #2513)This discussion was created from the release pex 2.18.0.
Beta Was this translation helpful? Give feedback.
All reactions