-
-
Notifications
You must be signed in to change notification settings - Fork 294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pex lock subset
fails for --style universal
locks when it traverses dependencies de-selected by environment markers tied to --target-system
and --interpreter-constraint
.
#2683
Comments
Ok, this is enough to repro: :; pex3 lock subset --lock lockfile.json click
There is no lock entry for colorama in lockfile.json to satisfy the transitive 'colorama; platform_system == "Windows"' requirement. |
Lock subsetting could crash previously. Also fix `pex3 lock {create,sync,update} --elide-unused-requires-dist`, which would not crash, but would fail to elide some dists. Fixes pex-tool#2683
The issue here was |
#2684 fixes both of these misses and brings |
pex lock subset
There is no lock entry for <package> in <lockfile> to satisfy the transitive <package>.pex lock subset
fails for --style universal
locks when it traverses dependencies de-selected by environment markers tied to --target-system
and --interpreter-constraint
.
@lecardozo the fix is released in v2.33.1. |
Discussed in #2682
Originally posted by lecardozo February 14, 2025
I'm trying to use the recently released
pex lock subset
subcommand to extract a subset of the dependency tree of an existing lockfile but I'm getting an error which I'm not sure is expected:Command
Initially I thought this was happening due to the lack of a
--complete-platform
specification — since there is a environment marker for a different platform associated with this dependency —, so I included the platform JSON file (generated by pex itself), but the error still happens.Question
Is this expected behavior? Should the lockfile indeed have an entry for this dependency?
Extra
The text was updated successfully, but these errors were encountered: