Pipenv or Poetry. Pip by itself is missing some key features, like separating dev dependencies (e.g. mypy)

I think it's a pretty common pattern to use

    pip install -r requirements-dev.txt

Not the most convenient, but solves (works around) the issue

Then you have to explicitly included all transitive dependencies for your dev dependencies, too. With Pipenv, only have to list your direct dev dependencies

These both use Pip internally. They are wrappers, not replacements.

Right. I was replying to a comment that asks if there was anything that improves upon pip, which both Pipenv and Poetry do

Pip has had ton of development in the last few years, and continues to do so. I'd say stick with pip, unless there's a specific problem you're addressing with pipenv or Poetry.

However, like a sibling comment, I've also heard god things about Poetry. Probably worth giving it a spin somewhere and seeing if my initial thought still holds.

I've been experimenting with Hatch:

https://hatch.pypa.io/

The USP of Hatch is that it uses the latest generation of Python standards and tech under the covers, so you have a unified tool that's less quirky than previous ones. Poetry and pipenv predate some of the improvements in Python packaging, so had to develop some things in their own way.

Poetry is the cleanest python deps handling experience, and I would recommend it as well.

But it is very slow.

I haven't tried it, but I've heard good things about poetry

I think people use Poetry for a variety of reasons, but I don't think speed is one of them.

Yeah, Poetry is definitely slow. This issue covers things:

https://github.com/python-poetry/poetry/issues/2094