4 ms·
I find Python is very prone to a lot of breaking changes even with minor version changes. And not just that, even minor versions have to match up specifically w
by aclatuts 4y ago
I find Python is very prone to a lot of breaking changes even with minor version changes. And not just that, even minor versions have to match up specifically with another libraries minor version. It seems to be a community or ecosystem problem with Python, which is why I avoid Python as much as possible.
In every other ecosystem when minor version are updated there are very rarely issues, and there are little issues with compatibility with minor versions of libraries.
- skrtskrt 4y agoeh, people love to break stuff on minor version changes of Go libraries to
- wizofaus 4y agoAt least you find out at compile time...
- btilly 4y agoMy (somewhat dated) experience says that Ruby is all the way worse than Python on this. In part due to a culture that encouraged monkeypatching. With the result that what behavior you get depends on who last monkeypatched it. So a dependency 3 deep that loads the module you expected to load last suddenly causes the monkeypatch you were depending on to disappear...
- treeman79 4y agoMonkey patching was the greatest thing ever. Until the community realized how bad it was. Don’t see it much these days