Once your project is setup, dependency management is what you do once in two weeks perhaps. Rest is just writing code.
The same issues exist in C, C++, Java and nobody seems to be complaining about those at the same volume.
This is why it doesn't seem so bad if you're programming in those languages.
Poetry is not the most used (or known) dependency management in Python.
What needs to happen is standardization - this has been done in java because of it's maturity. There's almost no java project that isn't using the standard maven dependency management (even projects that don't use maven, such as gradle projects, would use maven dependency management, and export themselves as an artifact usable via maven).
First of all, Poetry locks every dependency (even transitive ones) to the version you know works. This solves the problem of the project not using dependency management properly.
Secondly, setup.py allows you to specify your dependencies there, so most libraries use and specify that, which means that that isn't that much of a problem in Python. Sure, sometimes it is, but I haven't run into that particular problem very often.