Even fundamental functions like print work differently between Python 2 and 3, making it non-trivial to move from one platform to another.īut why hasn’t the whole world switched over to Python 3? The main problem is that there’s a lack of compelling motivation. That means that programs written for a Python 2 interpreter won’t run on a Python 3 interpreter. However, alongside those new features, Python 3 also has a problem: it’s not backwards compatible with Python 2. They wouldn’t be totally wrong since Python 3 includes some cool new features that Python 2 does not have. 2to3 or not 2to3?Ī naive user might think that Python 3 is better because it’s newer. If this seems like a large gap between versions, that’s because it is. But the newer version isn’t necessarily better: Python 3 isn’t backwards compatible with Python 2, and most developers are still using Python 2. New Macs still ship with Python 2.7.10, even though the most recent stable release is Python 3.5. For most user apps, you’d be right, but for underlying frameworks it’s a different story. You might think that your brand-new Mac has the newest version of all the relevant software.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |