id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
23446	mysqldb1 is no longer maintained and should not be recommended	frewsxcv	nobody	"Currently, the [https://docs.djangoproject.com/en/1.7/ref/databases/#mysql-db-api-drivers documentation] recommends [https://github.com/farcepest/MySQLdb1 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 [https://github.com/farcepest/MySQLdb1/issues/45 1] [https://github.com/farcepest/MySQLdb1/issues/49 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 [https://pypi.python.org/pypi/mysqlclient/1.3.2 mysqlclient]. A diff between mysqlclient and mysqldb1 can be found [https://github.com/PyMySQL/mysqlclient-python/compare/farcepest:master...master 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."	New feature	closed	Database layer (models, ORM)	dev	Normal	fixed		frewsxcv django@…	Ready for checkin	1	0	0	0	0	0