-
Notifications
You must be signed in to change notification settings - Fork 7
Tricky case: pyrax==1.9.8 -- pip._vendor.resolvelib.resolvers.ResolutionTooDeep: 100 #19
Comments
Whee! Thanks for trying out the new resolver @AndydeCleyre and for filing this report! ^>^ |
@AndydeCleyre Could you try out pip's current master branch (installable via |
This eventually fails:
It creates that dir during the process, and the result is the same with |
I feel I’ve seens this before… @pfmoore is this the error you managed to avoid by aggressively caching the candidates? I wonder why it’s coming back. |
I filed pypa/pip#8282 with a minimal reproduction of the failure. |
I got that today while testing something. I'm pretty sure it's a symptom of preparing the same ireq twice, but I'm not sure what triggers that - we'd need two candidates built from the same ireq. I'll try to take a look. |
I'm not familiar with this repo but FYI this particular example |
Yup -- this was used to collect interesting test cases during new resolver work that was undertaken in 2020. Before that, this was where I was drafting an implementation that ended up being very similar to resolvelib. :) |
20.0.2-601-g97f63905
3.8.2
linux
x86_64
poetry
1.0.5
pyproject.toml
:poetry.lock
:The text was updated successfully, but these errors were encountered: