This is simply not the case. It works sometimes. Maybe.
In many cases (software that is, say, a few years old) you run into packages that aren't available for a certain version. After trying various combinations of pip, maybe even easy_install, and poetry - to come up empty handed, you may realize you need some old library such as qt4, where pypi will certainly not work.
So when poetry or pip doesn't work and pypi doesn't have your specific old version, you may try mamba/conda/ micromamba conda-forge.
But these also probably don't have it either, and your stuck trying to compile old versions in a docker, which still is not guaranteed to work.
There's a reason that package dependency keeps getting rewritten in python. People think they can make it better, but some of the problem is actually just the developer choices by people making the packages. Probably the price paid for having too many people using the language who aren't actual software developers.
I don't know if this is off topic, but I cannot describe the amount that I miss the joy of `python -m venv` in other dynamic languages like ruby. I'm sure there are 100 different tools on github that claim to fix it, but "There should be one-- and preferably only one --obvious way to do it." makes me feel safe in trying out new conflicting libraries in a disposable environment
There's a reason that package dependency keeps getting rewritten in python. People think they can make it better, but some of the problem is actually just the developer choices by people making the packages. Probably the price paid for having too many people using the language who aren't actual software developers.