Support pex3 cache operation at the distribution level.
#2528
Assignees
Labels
Comments
jsirois
added a commit
that referenced
this issue
Oct 5, 2024
Use a `dbs` cache entry for all databases starting with PEP-691 fingerprints and hide this cache entry as a choice when purging individual entries using `pex3 cache purge`. Work towards #2528.
|
Arguably even better would be the ability to prune items not recently used. This requires the least understanding of Pex cache internals and is likely the most familiar metric. I'll land this capability 1st since it requires much of the same infrastructure needed to support the OP. |
jsirois
added a commit
to jsirois/pex
that referenced
this issue
Nov 4, 2024
Work towards pex-tool#2528.
|
#2586 provides most of the infra needed for this. |
jsirois
added a commit
that referenced
this issue
Nov 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be useful to be able to manipulate distributions in the Pex cache since these are the chief contributors to cache size and the cache items most directly identifiable to an end user since they ask for them in requirements.
Subject to spelling, the actions would be:
pex3 cache adda distribution to prep for offline use.pex3 cache removeone or more distributions safely (paying mind to unzipped_pexes and venvs symlinks).pex3 cache listto list distributions and their sizes much like the broader pex3 cache info.The text was updated successfully, but these errors were encountered: