-
-
Notifications
You must be signed in to change notification settings - Fork 644
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
[python] interpreter_constraints
is not used as the default IC for user resolves.
#17978
Comments
@benjyw Does the recent default IC deprecation resolve this? |
AFAICT this isn't necessary now, but the proof is in the CI run for #19065. Note that running However, I'm not sure why this was ever necessary. I synced back to #17957 and the same diff worked in the same way. |
These lines (which are all the places I've found where resolves_to_interpreter_constraints is consulted) imply that the right thing is happening:
|
@jsirois am I missing something? Do you remember what the evidence was that this was necessary? |
If I go back to the linked Pex 2.1.120 upgrade PR where it hit main: 505ab26 Then comment out the edit:
I find:
Note the IC on the last line just above. |
Ah, right. So this is not a Pants core bug, but a bug in the (old) generate lockfiles script? |
I think so, raw |
Yep - this is the nonsense:
|
Yep, verified that the new script is fine, so will close this. |
As of Pants 2.16.0.dev4 (main HEAD currently), the following configuration is needed to ensure the
python-default
resolve gets the repo-local default IC and not the Pants-embedded default IC:pants/pants.toml
Lines 130 to 147 in 05b9465
This feels like a bug. If the default ICs written down by the user are not picked as the default IC for a resolve written down by a user, what is the default IC used for then?
The text was updated successfully, but these errors were encountered: