4 ms·
It's clear the py2 to py3 migration was painful but I'm curious to hear how you would apply "they should fork / rename the language" here. To me it just feels
by halfdan 5y ago
It's clear the py2 to py3 migration was painful but I'm curious to hear how you would apply "they should fork / rename the language" here.
To me it just feels like semantics. They said "here's a new major version of python" when they could also have said "we have forked python 2 and we're calling it python 3. We think it's better and we will probably abandon python 2 at some point".
- necovek 5y ago(FWIW, "semantics" would be "what it means", so I figure that's not what you wanted to say: from your example, I guess you are saying it's more that it's a different wording — syntax? — for the same meaning) But it's about setting expectations. The only problem I ever had with py2 to py3 migration was that it was even possible to have the same codebase run against both, when languages are incompatible to such a degree (most notably, basic type has changed). It basically forced people to make the worst use of the Python dynamic nature (as soon as the stdlib started doing that, there was no going back).
- quietbritishjim 5y agoSemantics refers specifically to meaning of words/language. If you say "it's only semantics" then it probably means you both understand and agree on the concepts but not the meaning of the words surrounding those concepts. That applies in this case, with the concept being breaking changes to a language along the lines of Python 2->3, and the terms being "version change" and "new language".
- necovek 5y agoMakes sense, thanks.
- verdverm 5y agoWas? It still is painful as some companies have decided to keep and support python2 for another 5+ years. I have programs which require the same dep from different pythons. To me, Python represents how not to do language versioning.