3 ms·
It's not like regular tools need to break with each new Python realease. It's mostly endless tinkering, attention deficit, and bad choices. Heck, even within t
by coldtea 4y ago
It's not like regular tools need to break with each new Python realease. It's mostly endless tinkering, attention deficit, and bad choices.
Heck, even within the same Python release, I never understood why we need to be in the 2000+ update of pip, for example, and it needs to update itself almost every month or so. It's a ducking dependency installer, just formalize the design and protocols already and keep it at that.
(For context, I never had that issue with npm. Not to any same-order-of-magnitude comparable level at least).
- nmalx 4y agoPython/pip criticism is downvoted again. The Python propaganda arm is strong as ever. No other language relies on marketing and censorship that heavily.
- Ingaz 4y agoI encountered problems with dependencies in python projects only when AI/ML libraries were used pytorch/scikit-learn/etc NPM on the other hand: it broke in every project and in trivial cases. E.g. upgrade of postgresql lib. I hope that deno/smth other will make possible to forget npm finally
- HelloNurse 4y agoIt's more the fault of broken libraries (remember that you depend on the weakest link out of hundreds or thousands of random strangers) than of inadequate tools.