#23446: mysqldb1 is no longer maintained and should not be recommended
-------------------------------+--------------------------------------
     Reporter:  frewsxcv       |                    Owner:  nobody
         Type:  Bug            |                   Status:  new
    Component:  Documentation  |                  Version:  master
     Severity:  Normal         |               Resolution:
     Keywords:                 |             Triage Stage:  Unreviewed
    Has patch:  0              |      Needs documentation:  0
  Needs tests:  0              |  Patch needs improvement:  0
Easy pickings:  0              |                    UI/UX:  0
-------------------------------+--------------------------------------
Description changed by frewsxcv:

Old description:

> 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
>
> If others agree, I would be happy to write the copy in the documentation
> to support this change.

New description:

 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.

--

--
Ticket URL: <https://code.djangoproject.com/ticket/23446#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.b730213a17edf15bd208671cf3190367%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to