5 ms·
Python made the unfortunate but understandable decision to split the community. It's really hard to make a non-backwards compatible change in an open source co
by moxious 10y ago
Python made the unfortunate but understandable decision to split the community. It's really hard to make a non-backwards compatible change in an open source community because you can't make anybody move.
My $0.02 is that Python 3 is clearly better, and that if you'd use python for something new it should be 3. But I also think it's unfortunate that the community is in the sort of state where people ask this as a legitimate question in 2017.
Progress requires python 2 die, but it's taking its sweet time.
- xrange 10y agoCan anyone point me in the direction of information of why is would be so hard to have a from __ancient_history__ import print_statement, etc. ...especially now that most of the big projects that are ever going to get converter have been converted? Even if it was slower / used more memory / etc. for those programs that did use that pragma.
- fiedzia 10y agoBecause python 3 made hundreds of small changes here and there. Supporting them all would not be possible. The problem is not speed and memory, but complexity of the interpreter.
- xrange 10y agoI was more thinking that the compatibility layer would maybe suck in a whole python 2 parser, and potentially even the interpreter, operating on potentially common objects in memory. But just how different are the bytecodes for 2 vs. 3? Even if they were very different, I guess my question is, how hard would it be to transpile 2 bytecode into 3 bytecode. I'd think it would be loads simpler than what Jython does on the JVM for what I can only imagine must be a radically different virtual machine and memory model. I guess the real answer is probably more political rather than technical.