Re:Why Python 3 Exists
by brightsize on Thursday December 17, 2015 @02:34PM
(#10753846)
What about Google's AppEngine? I would dearly love to run Python 3 code on it, but 2.7 is the latest version that's supported. Google seems to have no roadmap to Python 3 on the platform (Managed VMs don't solve the problem - the SDK does not support Python 3) which leads me to worry that they're going to deprecate support for the language entirely on it.
Re:Why Python 3 Exists
by alextgordon on Thursday December 17, 2015 @12:33PM
(#10752855)
History it isn't. There is a vast amount of Python 2 code in existence. I still write a lot of Python 2, doing maintenance on existing projects.
Re:Why Python 3 Exists
by mwcampbell on Thursday December 17, 2015 @12:12PM
(#10752696)
What about MySQLdb? That's the main extension module that has been keeping me on Python 2 for server-side software. That, plus a lack of perceived upside to CPython 3, which is still an interpreter with a GIL after all. PyPy 3 might be compelling if it can run MySQLdb or a bug-compatible replacement. True, PyPy still has a GIL, but at least it also has a JIT compiler.
MySQLdb has other issues besides Python 3 support. It's no longer maintained and hasn't been updated in quite some time. The Django documentation (and I) now recommends mysqlclient-python, which is compatible with systems that rely on MySQLdb
Another endorsement from me. We migrated with
import pymysql as MySQLdb
Re:Why Python 3 Exists
by andrewstuart on Thursday December 17, 2015 @12:18PM
(#10752734)
Re:Why Python 3 Exists
by BuckRogers on Thursday December 17, 2015 @01:47PM
(#10753465)
Check into PyPy-STM, they were able to remove the GIL. This will eventually be merged back into PyPy4 (the 2.7 compatible version).
Really this topic is coming to an end. Most libraries support Python 3 and if they don't there's better alternatives.
For new users and new projects there's no reason now except personal preference to choose Python 2 and in fact beginners who start with Python 2 are just instantly incurring a learning debt upon themselves to be paid down the track when they have to move to Python 3.
The community has some extremely vocal Python2 diehards but their arguments no longer hold water.
>>why has Python 3 adoption been so slow? Whatever, it's just history now.