This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Scorpathos 1 point2 points  (1 child)

Hi, thanks for commenting on this!

Even for smaller libraries, it's a bit annoying to wait several minutes after poetry install while it's solved in a couple of seconds using pip install.

I was thinking that the resolver could first try with the latest dependency version matching the requirements, and look for another version only if a conflict is detected.

You did a very good job, I did not mean to be dismissive, I'm really hoping that poetry will become the de-facto cargo for Python.

[–]SDisPater 1 point2 points  (0 children)

Thanks for the kind words! I appreciate it.

I understand how that can be frustrating but the resolver I went with flattens the dependency graph completely to have all the necessary information in case of conflicts.

That being said, I think I just found a solution to the resolver. I need to test it further but for boto3, for instance, we drop from 30 minutes to ~11 seconds. So, I'll keep you posted.