4 ms·
The heartbreaking thing is that if you're willing to only target 2.7 on the Python 2 front, it's relatively trivial to write in Python 3 and have it be immediat
by haikuginger 9y ago
The heartbreaking thing is that if you're willing to only target 2.7 on the Python 2 front, it's relatively trivial to write in Python 3 and have it be immediately compatible in Python 2 using from __future__ imports.
- ericfrederich 9y agoFor trivial programs sure... not when dealing with encoders, decoders, binary formats, etc, etc. It all depends on how they wrote their Python 2.7 code. You can write it oblivious to Python 3 and screw things up, or you can write it in a way that you know you'll eventually support Python 3. In the latter case, you might as well just support both right away though.
- spooneybarger 9y agoAndy's next blog post is going to be in this general area. Check back next month!