Bug#768096: [Python-modules-team] python mysqldb on python 3

[Scott Kitterman <debian@kitterman.com>]

On Tuesday, November 18, 2014 04:02:14 PM Brian May wrote:
> On 18 November 2014 15:40, Scott Kitterman <debian@kitterman.com> wrote:
> > Is the original development inactive?  I think it would be at least
> > somewhat
> > anti-social to switch to a non-friendly fork (no idea if that's relevant
> > here).  What are the circumstances around the fork.  I think that's at
> > least
> > socially significant.
> 
> I am no expert here. Looking at source force, the latest stable release of
> (1.2.3) mysqldb was 2010-06-17 (with the corresponding windows msi being
> generated 2012-09-05).
> 
> http://sourceforge.net/projects/mysql-python/files/mysql-python/1.2.3/
> 
> There has been a beta version since (1.2.4b4), having problems getting a
> date for it using source forge.
> 
> Last svn commit appears to have been made 2012-09-24.
> 
> The big issue mysqlclient solves is Python3 support, although I suspect
> there are other bugs fixed too.
> 
> https://pypi.python.org/pypi/mysqlclient/1.3.4
> 
> Looking at mysqlclient at https://github.com/PyMySQL/mysqlclient-python,
> there is the text:
> 
> "This project adds Python 3 support and bug fixes. I hope this fork is
> merged back to MySQLdb1 like distribute was merged back to setuptools."
> 
> A merge back would be good, but unfortunately I am doubtful it is going to
> happen.

That does sound like a friendly fork, so I think taking over the package name 
for Stretch would be appropriate, but in the meantime, it should stay in 
experimental in case a bug fix is needed for the current package for Jessie.

Scott K