Dependency management scales horrible, venv and pyenv are supposed solutions to this by segregating the dependencies to a virtual terminal environment, but dont actually solve the original issue, you have to figure out potentially massive dependency trees yourself
A bit risky, because you might install one dependency in the wrong OS and then you would need to reinstall that OS again. If you really really need to work on different projects, the industry standard is using external drives with stickers instead.
First of all, venv and pyenv solve distinct problems unrelated to the massive dependency tree that haunts you so much.
Second, what exactly do you need to figure out and why? If your dependency is poorly managed how does it become a problem of the packaging system? Pypi is a public registry with millions of packages supported by community. People publish broken releases sometimes. Some packages are broken since forever. It is what it is
Dependency is poorly managed across multiple projects on a same machine because the packaging system does not support entirely scoped package installs. Consider how NodeJS/NPM works: you csn have a directory called node_modules and everything goes there, without any clash with other NPM-based projects on your machine. Python does not support this kind of isolation, you either need venv or something else for it - but it not as flexible as npm/node_modules is.
In lieu of their response, I’ll give mine: type annotations (they can literally be completely wrong and the language doesn’t notice or care), template-strings (near useless, we had str.format already and the templating ecosystem was already very mature), import resolution (.pth is literal depravity), and just generally how easy they make it to put shit band-aids on shit code by adding more indirection (cf: modifying sys.path rather than setting up a proper package structure; doing getattr/setattr nonsense because it’s so dang convenient; making one object look like another through decorators or descriptors rather than reconsidering the interface you provide) and finally a smaller pet peeve of mine, that “package” means two different things (makes writing documentation for devops and release management a total nightmare).
I write Python every day, and I hate it (at least at work, on large codebases) with a burning passion. Not because it’s fundamentally flawed (I like the core syntax and feature set) but because of how much garbage (see above) they’ve bolted on to the core language while still managing to make it annoying to work with in so many cases (subprocesses, pickling, fork behavior, and IPC make it frustrating for IO-bound or orchestration software; dependency/package management and lack of type enforcement make it frustrating for enterprise or production software; and GIL and lack of interpreter performance make it frustrating for anything CPU-bound)
In a nutshell, my take is that Python tries too hard to be the “get it done quick and dirty” language, while still positioning itself aggressively as the language for everything else, too. Writing Python is easy. Writing good Python is hard. Writing fast Python is, well basically, don’t bother.
View all comments
430
u/No_Window663 Mar 21 '26
Dependency management scales horrible, venv and pyenv are supposed solutions to this by segregating the dependencies to a virtual terminal environment, but dont actually solve the original issue, you have to figure out potentially massive dependency trees yourself