This article someone linked is not 14 years old and it perfectly describes the mess python and pip are: https://chriswarrick.com/blog/2023/01/15/how-to-improve-python-packaging/

My favorite part is:

Most importantly: which tool should a beginner use? The PyPA has a few guides and tutorials, one is using pip + venv, another is using pipenv (why would you still do that?), and another tutorial that lets you pick between Hatchling (hatch’s build backend), setuptools, Flit, and PDM, without explaining the differences between them

But yes, following old blog post is the issue.

They're not difficult by any means.

But they are tedious when compared to other solutions.

cargo is the package manager for the Rust language

I've never had an issue with nuget, at least since dotnet core. My experience has it far ahead of npm and pip

cargo is rust

what's wrong with nuget? I have to say I like the "I want latest" "no, all your dependencies are pinned you want to update latest you gotta decide to do it" workflow. I can think of some bad problems when you try to do fancy things with it but the basic case of "I just want to fetch my program's dependencies" it's fine.

Try not to learn too much from memes, they're mostly wrong. Conda is good, if you're looking for something more modern (for Python) I'd suggest Poetry

vevn is not pip. The confusing set of different tools is part of the problem.

cargo just works, it's great and everyone loves it.

npm has a lot of issues but in general does the job. When docs say do 'npm install X' you do it and it works.

pip is a mess. In my experience doing 'pip install X' will maybe install something but it will not work because some dependencies will be screwed up. Using it to distribute software is pointless.

Pip stores everything inside of some random txt file that doesn't differentiate between packages and dependencies.

It's all fun and games until the wheel variant you need for your hardware acceleration package conflicts with that esoteric math library you planned on using.