5 ms·
Great, so now not only Python will be incompatible with itself, but also incompatible with itself even if you use Python 3. Sigh.
by jeffrallen 4y ago
Great, so now not only Python will be incompatible with itself, but also incompatible with itself even if you use Python 3.
Sigh.
- anakaine 4y agoOr, the glass half full view of the world suggests that low usage high barrier to maintenance module deprecation increases overall long term improvements and compatibility at the cost of small, planned, notified, short term inconvenience.
- dbsmith83 4y agoI think you're missing the point. Nothing is wrong with deprecation, but it should be done properly. Ideally, breaking changes should correspond to a major version increase
- drexlspivey 4y agoYou should sign up to maintain those ancient modules
- xigoi 4y agoWhy do they need to be maintained? Just leave them as is.
- ciupicri 4y agoBecause supposedly people will report bugs for them and someone will need to fix them.
- slig 4y agoCode rots.
- samus 4y agoApart from requiring security fixes, they also sometimes block changes and newer features. At that point, the maintainers might have to choose between breaking the obsolete module or shelfing the feature/fix. Deprecations are the way to indicate that support for the module will be eventually dropped. There is no reason to leave those modules there if they cannot be relied on.
- CJefferson 4y agoSeveral groups of people offered to maintain python 2. They were told very clearly they could not do so "officially", and we're even threatened with lawyers if their thing looked like it could be mistaken for "Python 2".
- CogitoCogito 4y agoSo don’t maintain it officially and use a different name. What’s your complaint exactly?
- acdha 4y agoDo you have pointers to that? The one I saw was called “python 2.8” which is definitely a point of confusion for people who might think it was supported.
- mixmastamyk 4y agoLook up Tauthon , believe that was the name.
- acdha 4y agoYes, that’s the one. Note that they’re still there – the PSF just didn’t want them calling something which isn’t made by the Python developers Python 2.8. Once they adopted the Tauthon name they were fine.
- int_19h 4y agoHere's an actively maintained version of Python 2: https://www.activestate.com/products/python/python-2-7/ https://www.activestate.com/products/python/python-2-7/ As you can see, it is still offered, and the PSF doesn't have a problem with that. The problem with those other groups is that they didn't want to maintain Python 2. They wanted to take it and develop it, evolving the language separately from Python 3 - while also calling the result "Python 2.8" (and presumably later Python 2.9 etc). It stands to reason that people who own the brand don't want it to be associated with a third-party fork that's making its own major design decisions, no?
- qikInNdOutReply 4y agoHave you tried Lua.. they brake for noone..
- yoyohello13 4y agoWhat? Lua has breaking changes every release.
- qikInNdOutReply 4y agoExactly.