mysqldb1 is no longer maintained and should not be recommended
Currently, the documentation recommends mysqldb1. Here is why this recommendation is hurting the community, especially new users using MySQL with Django:
- mysqldb1 is not compatible with Python 3
- mysqldb1 has not had a commit since November 2013 (besides one tox commit from January 2014).
- mysqldb1's author, farcepest, is not addressing any of the GitHub issues (and is inactive on GitHub in general)
- the latest version of mysqldb1, 1.2.5 has a regression from its previous version 1 2 and it has not been addressed
In an attempt to solve this dilemma, I propose we stop recommending it as a MySQL driver in the documentation.
In replace of it, I would like to recommend a fork called mysqlclient. A diff between mysqlclient and mysqldb1 can be found here. Some of the benefits of mysqlclient over mysqldb1:
- mysqlclient supports Python 2.7 and Python 3.x (same as Django)
- mysqlclient is authored by the same team that authored PyMySQL and much more active
I've used the library for a couple months now and have not run into any issues. If others agree, I would be happy to write the copy in the documentation to support this change.
Change History
(11)
Description: |
modified (diff)
|
Description: |
modified (diff)
|
Component: |
Documentation → Database layer (models, ORM)
|
Triage Stage: |
Unreviewed → Accepted
|
Type: |
Bug → New feature
|
Triage Stage: |
Accepted → Ready for checkin
|
Resolution: |
→ fixed
|
Status: |
new → closed
|
There's a thread related to this on the DevelopersMailingList: https://groups.google.com/d/topic/django-developers/n-TI8mBcegE/discussion
Unfortunately, it hasn't gotten many replies. Perhaps you could chime in there as that's the place where we'd make this sort of decision.