Likely even a little bit more narrow than Python-only since it seems to be Poetry-only. Most Python projects probably work okay with Poetry, but it's still a relatively new tool compared to the other options.
Translation: I've never used poetry, don't know anything about it, and I'm going to talk out of my rear end and assume that it doesn't use conventional, existing venv/pip under the hood.
There isn't a single python project out there that can't be worked on with poetry. It creates a venv. Poetry is doing a lot of things to manage automatically activating and deactivating it, etc, but it's just a venv.
https://github.com/python-poetry/poetry/issues/4231
Is one issue. If you even transitively depend on pytorch poetry will break and you will need hacks to make it work or just give up.
also, a lot of python packages don't seem to follow the idea of semvar very well. Especially when you compare it to other communities like Go.
> The Python environmental protection agency wants to seal it in a cement chamber [...]
Also, it really doesn't work super well if you need to work on multiple development projects simultaneously, and when "just change the way you structure your entire project" is poetry's answer to this, the solution is "okay we won't use poetry".