Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Poetry package install time seems longer than installing with pip #338
I am reasonably sure that installing packages using
To compare. Here is a
Here is another build with
In both cases, both dev and non dev requirements were installed.
Thanks for your interest in Poetry!
This is expected because Poetry orders the packages to install so that the deepest packages in the dependency graph are installed first to avoid errors at installation time. This requires sequential installation of the packages which takes longer but is more "secure".
Also, Poetry checks hashes of installed packages for security reasons and due to the way
I intend to improve the installation part of Poetry sometime in the future to speed things up, yes. I can't give you an ETA though, the only thing I can tell you is that it will likely be after the
I'll be sure to keep you posted if anything changes on that front.
Let me start by saying I recently discovered
Now, is there any progress on this? I just migrated a couple of projects to poetry and my container builds went from 2s to 5 minutes each. The reason why it's so slow is twofold:
so I could cache that layer. With
Which means I need to install the dependencies over and over even though I haven't changed a single dependency. I am trying to do something equivalent with:
But I am not sure if this is the right thing to do but does the job. Feels extremely hacky so I'd appreciate some advice :P
Re this previous comment, it would be ideal if there was an interface to install when only the lock file is available, so that we can continue to make good use of docker layer caching. Because I haven't been able to get an install to succeed when the source isn't also available.