News for hackers. Stuff that matters.

A comment on Why Python 3 Exists. Parent comment

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.
[ Parent | on HN ]
Re:Why Python 3 Exists by frewsxcv on Thursday December 17, 2015 @12:50PM (#10752998)
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

https://github.com/PyMySQL/mysqlclient-python

[ Parent | on HN ]
Re:Why Python 3 Exists by kstrauser on Thursday December 17, 2015 @02:32PM (#10753831)
Another endorsement from me. We migrated with

    import pymysql as MySQLdb
and everything just worked.
[ Parent | on HN ]
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).
[ Parent | on HN ]