recent work has cleaned up the big horrible stacks that poetry used to show whenever the smallest thing went wrong, which is great. But it has overshot slightly.

Example: create a project called requests, and then poetry add requests.

In an ideal world we'd get a nice clean error message saying that a project can't be a dependency of itself. But:

$ poetry add requests
Using version ^2.28.0 for requests

Updating dependencies
Resolving dependencies... (0.0s)

huh, that looks fine.

In fact poetry has hit an assertion, which you will see if you poetry add requests -vvv, and fallen over: but it has almost completely hidden this from the user.

('almost' because the exit-code is non-zero, so that's good).

This particular assertion isn't the point, the point is that when poetry does bug out it now does too good a job of disguising that.