Replies: 3 comments 2 replies
-
Could be unrelated but I hit something similar in In my case I had to clear Poetry's cache to get Poetry to work properly again. |
Beta Was this translation helpful? Give feedback.
-
As said,
I do not understand those statements, in particular the first: why does it say "no versions of metapensiero-tool-tinject match >1.0,<2.0"? Does this ring any bell? |
Beta Was this translation helpful? Give feedback.
-
After several debugging sessions, I think I found the cause. As said, the package that causes the problem is one of mine, metapensiero.tool.tinject: for the recently released v1 it uses hatchling as build system. The package declares a dependency on The never ending loop that I get with poetry 1.1 happens because it:
The cause of this is in the So, should I convert this Thank you for any feedback! |
Beta Was this translation helpful? Give feedback.
-
I'm seeking an advice on how to investigate, and hopefully resolve, a problem I hit today.
The following very simple
pyproject.toml
, created withpoetry init
(v1.1.13), has a single dependency against a project of mine:Executing
poetry install
enters into an infinite loop, and with-vvv
I can see:The same configuration works with
poetry 1.2.0b2
:Apparently the problem is related to a new 1.0 release of metapensiero.tool.tinject that I made yesterday, but I really cannot understand what I did wrong to break poetry resolver 😭. The fact that both
pip
andpoetry 1.2.0b2
correctly install it seems to suggest that the package is correct...I'd appreciate any hint on how to proceed.
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions