Hello everyone. I don't know why, but after cloning my project and rerunning

./pants generate-lockfiles --resolve=python-default

, the execution is stucked and I don't know what to do. Usually it takes 1mn30 to finish, but after trying several things, I wait more than 20min and nothing changes. I use Pants 2.12.0 and I'm on Ubuntu (WSL on Windows 11). I didn't change my lockfile and it only happens on

python-default

, no problem with

black

,

flake8

, etc. Any suggestion?

What is it printing? There was a similar bug I hit in pants, it’s fixed in an unreleased commit in

2.13

.

@ancient-france-42909 Hi. It's just running forever. Is there a flag to have more verbose output?

Okay, so not my issue. 🙂 Yes, add

-ldebug

as a global option.

Okay it was stuck because I had

pyscopg[c]

as a dependency and I didn't installed the

libpq-dev

Ubuntu package. It's curious that the command doesn't just fail.

This was Pip in the background taking a very very long time to resolve

pyscopg[c]

In order to do so it had to try to build probably nearly every version from source in serial... all to eventually fail.

Because it’s 2022 and we still don’t have a way to figure this out except downloading every single possible version of every package you want to install 🙂

But that's because its not 2022. Python was written in ~1990 and it did not have the benefit of a big corporate backer or hindsight like rust / go etc that now build all this stuff in up front. As such, there has been 30 years of folks - volunteers for the most part - trying to figure out a way to do 3rdparty deps and its ugly as most organic things are.

https://www.pypa.io/en/latest/help/ 🙂

I tested it with Poetry, and it immediately failed. I didn't know it worked like that with pip. Thanks for the explanation.

It may be better with newer Pip. I'm just finishing work on upgrading Pex (which Pants uses) from Pip 20.3.4 to 22.2.2.