For 2.32.x, filed <pants uv issue repro #23354> B...
# development
w
For 2.32.x, filed pants uv issue repro #23354 Bug 1 - maybe more of a pex bug Bug 2 - between Pants/pex. Didn't dig yet.
at least claude claims they are the same:
Both bugs share the same root cause: once PEX satisfies a package from a no-extras req_string, a subsequent req_string for the same package with extras is treated as already resolved — the extras are never activated.
tested with uv off:
Copy code
+++ b/uv-extras-repro/pants.toml
@@ -6,7 +6,6 @@ backend_packages = ["pants.backend.python"]
 [python]
 interpreter_constraints = ["CPython>=3.10"]
 enable_resolves = true
-resolver = "uv"
it repros too, so probably more signal this is a pex issue. given this, this is probably not pants release blocking. nvm without
uv
, they both work, so this is breaking existing behavior.
Resolved via https://github.com/pantsbuild/pants/pull/23354#issuecomment-4467807264, so may need a bump on pex and cherrypick to 2.32.x.
f
cherry-pick PR: https://github.com/pantsbuild/pants/pull/23356 (someone else will need to approve since the auto cherry picker failed)
1