5 ms·
I personally think they should have just declared Python 3 to be a new language, inspired by python 2, like many other competing new-pythons. Instead, they did
by Chris2048 10y ago
I personally think they should have just declared Python 3 to be a new language, inspired by python 2, like many other competing new-pythons.
Instead, they didn't play fair, and gave themselves an unfair advantage.
- scrollaway 10y agoDamn that Python team, giving themselves an unfair advantage in developing Python. Seriously, what am I reading here?
- krick 10y agoMaybe this is a joke, and then I'd say it's pretty neat one. I mean, just look at that, what other language got a similar problem of that scale! And let's not pretend it all passed and we are happily moving forward: this year (this month, actually) I've seen very prominent NN-course, suggesting Python 2.7 for all assignments and code samples, and quite useful library (also NN-related), supporting 2.7 only. I guess, some of mitsuhiko's (Ronarcher's) developments didn't move to 3.* as well. So, yeah, IPython dropping 2.7 is pretty huge. Almost like moving to a different language.
- jerryszczerry 10y ago> I've seen very prominent NN-course, suggesting Python 2.7 for all assignments and code samples, and quite useful library (also NN-related), supporting 2.7 only. Oh, that's plain silly. Isn't the whole point of Python 2.7 to facilitate the transition to Python 3?
- krick 10y agoSilly or not, but it's still very common mindset with scientific-oriented people (who care about ML, econometrics, statistics and such much more than "programming" per se), who form a quite notable category of Python users. Actually, for me they are the reason why I'm still using Python a lot (although I try to stick to 3.x), because for other use-cases, like scripting or web-dev I mostly (but not completely) moved to other languages.
- Chris2048 10y agoWhat defines python? You purposely ignored the distinctions I clarified in my post. Let's say I developed a python-like language called "schlython", can I call on the python-2 community to convert all "old" python-2 code into my competing language?
- pekk 10y agoLet's say you developed a Python-like language called Python 2.6, can you call on the Python-2.5 community to convert all old code? Come on, nobody was forced at gunpoint to port to Python 3, that's why there are still abandoned Python 2 projects all over the Cheese Shop.
- Chris2048 10y agoWhat conversions are needed for the py2.6 code? > nobody was forced at gunpoint The caretakers of py2 are the promoters of py3. Support was dropped for py2 without any serious effort to find new caretakers, so that the demise of py2 would promote switching.
- scrollaway 10y agoEnough with the conspiracy theories already. There was no reason to find "new caretakers" for Python 2.7 because it's simply an old version of the language. Reading through your posts here, I don't know what your problem is with the Python team, but please do get over it. It's incredibly annoying dealing with someone who just seems to think they're entitled for more than a decade of support of a version of their free product.
- Chris2048 10y agoWhat conspiracy theory - Who decides that py2 needs to be killed off? > but please do get over it This is an ad hom - please make your posts more substantial, it feels like you are the one with a chip on your shoulder if you can't respond to these points. Your original comment added nothing to the thread but snark.
- sigjuice 10y agoThere will be many Python 2 production codebases that will forever remain at Python 2. Whether Python 3 is a new language or not will not make a difference.
- cookiecaper 10y agoI really don't understand why. Python 3 is not a radical departure and the usual complaint is the dependency graph. Over the last 18 months that has really healed up, to the point where the Wall of Superpowers is almost 100% green. I understand that some people want to keep old code running as long as humanly possible, which is their prerogative. But there's no reason to imply that conversion to Py3 is unduly difficult or something that shouldn't be undertaken, even for large/complex codebases. If Google can write grumpy to transpile Python code to Go, there's no reason it can't improve 2to3 to handle their incompatibilities.
- scrollaway 10y agoI think the main issue is library compatibility, which gives people the impression that compatibility is an unreachable target. The truth is, once most libraries are 3.x compatible, porting is very easy (as easy as a 2.x -> 2.y transition). And now, we've reached that point. People are starting to catch up. There are some exceptions of course, those who heavily rely on 2.x unicode behaviour and such, but all in all they are rare. So now, it's much easier than it used to be.
- eikenberry 10y ago> as easy as a 2.x -> 2.y transition You mean I can just run all my python2 programs with python3 runtime with no changes at all. Because that was how every upgrade before python3 went.
- scrollaway 10y agoNearly all my code co-runs on 2.7 / 3.6 with almost no hacks. So, yes.