Bug#768096: [Python-modules-team] python mysqldb on python 3
On Tue, 18 Nov 2014 13:55:57 +1100 Brian May <brian@microcomaustralia.com.au>
wrote:
> On 5 November 2014 12:11, Collin Anderson <cmawebsite@gmail.com> wrote:
>
> > > There might be a problem because it looks like it conflicts with
> > python-mysqldb.
> > Yes, it's a 100% compatible fork intended to replace python-mysqldb. Same
> > python package name and everything. We could decide to only include it for
> > python3, or we could even have this completely replace the original
> > python-mysqldb on python2.
> >
>
> I don't much like the idea of having different code base for python2 and
> python3 versions.
>
> My current plan (unless anyone objects) is to replace the python-mysqldb
> package with the mysqlclient package, keeping the existing python-mysqldb
> (which makes sense as the python module name is unchanged).
>
> My initial upload will be to experimental.
>
> (as time permits)
The current package is pretty widely used:
Reverse-Recommends
==================
* bauble
* bley
* griffith
* papercut
* pwman3
* pyaimt
* pyicqt
* python-adodb
* python-authkit
* python-scrapy
* python-springpython
* python-sqlkit
* python-tornado
* python-webpy
Reverse-Depends
===============
* auth2db
* bauble
* blogofile-converters
* djagios
* emma
* epigrass
* neutron-common
* openmolar
* python-biopython-sql
* python-ceilometer
* python-cinder
* python-designate
* python-glance
* python-heat
* python-keystone
* python-mysqldb-dbg
* python-nova
* python-trove
* rddmarc
* viewvc-query
* zope-mysqlda
I'd suggest not just replacing it. How about call your package python-
mysqlclient (as you had originally intended I believe) and have it conflict
with python-mysqldb (since they both provide the same interface, conflicts is
appropriate). Maintainers can decide which they prefer and if we get a strong
consensus for Stretch, then we can remove python-mysqldb and have python-
mysqlclient provide it.
I think this way would be much friendlier and lower risk.
Scott K
Reply to: