pip install mypackage
No? it's too 2010?I've been a developer for some time now. All I know is a lot of developers love unnecessary complexity. It's even more true in the JS world to be honest.
Javascript modules were supposed to make everything easier yet some people still manage to write insane boilerplates and tools on top of that and bring back complexity where it is not needed.
The issue with blind use of pip is that it will inevitably break something in your system when a dependency upgrades too much. Hence virtualenv, and later pipenv.
And setting up a Python project is more than just dependency management. Do you want an egg/wheel/etc? Do you use setup.py, or is it deprecated? Speaking from experience, the docs for various Python tools simply don't agree on these things, and it's very hard to set up a project "correctly" without someone helping you.
The fact that a container is easy today just enables and hides the fact that it's a bit ridiculous to need one for half of the things we now use them for. Same for snap, flatpack, appimage, etc.
Rather than have a handle on my surface and interface with the os, I'll just bundle an os with my calculator app.
All because they're using a newer version of some library that maybe has an extra param on one function to automatically zero-pad or something.
And "they" isn't necessarily the developer of the calculator app but could be the developers of any of the hundreds of dependencies.
We all know all the excuses how we got here. We all know how each individual step along the way has it's excuse. Yet, it's not a great place we got to.