high-magician-46188
01/22/2023, 4:26 PM> pants generate-lockfiles --resolve=python-default
โ 4795.88s Generate lockfile for python-default
Is there anything I can do to debug it?
There is probably a bad constraint that wrack havoc, but I don't know which and there are 370 dependencies in the repo...happy-kitchen-89482
01/22/2023, 5:01 PMhigh-magician-46188
01/22/2023, 5:22 PM2.16.0.dev3
.
The interpreter constraints are ["CPython>=3.9,<3.11"]
.
I'd actually want to include 3.11 as well, but I'll wait with that since I still tackle other challenges.
Also, thanks for the quick reply ๐8487.55s Generate lockfile for python-default
.
So is there no way to debug it currently?happy-kitchen-89482
01/22/2023, 5:25 PMCPython==3.9.13
or something like that (whatever you have on your system)enough-analyst-54434
01/22/2023, 5:27 PMhigh-magician-46188
01/22/2023, 5:30 PMmacos_big_sur_compatibility = true
(IDK what macos_big_sur_compatibility
is and I didn't find documentation for it in the docs).
Is there a documentation on how to change the pip version?happy-kitchen-89482
01/22/2023, 5:33 PM./pants help-advanced python
and look for pip_version[python.resolves_to_interpreter_constraints]
high-magician-46188
01/22/2023, 5:50 PM[python]
interpreter_constraints = ["CPython==3.9.13"]
Made it complete it pretty fast.
So now I'm confused due to the python.resolves_to_interpreter_constraints
thing.
Also, I do need it to be resolved for 3.10 and 3.11 as well...3.9.1
, 3.9.2
, ...)pants help-advanced python
is really nice in terms of docs as well as the fact that it show the current value and where it comes from! ๐happy-kitchen-89482
01/22/2023, 6:17 PMdev4
and you're on dev3
, so maybe the issue is newly introduced.interpreter_constraints = ["CPython==3.9.13", "CPython==3.10.3']
, or still use ranges, but finer rangeshigh-magician-46188
01/22/2023, 6:37 PM22.3
and pip stopped with an error, rather than continuing into infinity.
I'll resolve it and hopefully it will let me lock afterwards.
Will report back if I find anything interesting (though it won't be today).
Thanks for everything ๐pants.toml
made the resolution much faster as well as flagging the underlying issue (which didn't happen with the default pip version set in Pants 2.16.0.dev3).
After I've fixed the underlying issue (which was in a package from another repo), the locking completed successfully and about as twice as fast as it was before.
My TL;DR is that I recommend setting 22.3
as the default version of Pip to be used by Pants, and barring that, at least add it to the documentation.