Re: python3-django and mysqldb
On Tue, Jul 8, 2014 at 9:24 AM, Brian May wrote: > Have CCed the maintainer (Debian Python Modules Team is uploader). > > Sandro Tosi, do you have any objections if I package the latest version for > Debian? it seems you uploaded anyway, but that's ok, thanks for the upload -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAB4XWXw2XD=a8vpiiUYY9TdOFNibtWZzsoVF=oowce2x-1h...@mail.gmail.com
Re: python3-django and mysqldb
On 7 Jul 2014 13:42, "Brian May" wrote:
> Which is already in unstable:
>
> python-mysql.connector
> python3-mysql.connector
Also see https://groups.google.com/forum/m/#!topic/south-users/hrxwgimaYy8
By default south doesn't work with mysql connector.
Fortunately the workaround seems to be simple enough. Not tested it myself
yet.
Quote:
You can do an equivalent in user code: In your settings, add
SOUTH_DATABASE_ADAPTERS = {
'default' : 'south.db.mysql'
}
To tell South that, although it doesn't know mysql-connector-python, it can
use its mysql backend to handle it.
Re: python3-django and mysqldb
On 7 Jul 2014 13:42, "Brian May" wrote: > Which is already in unstable: > > python-mysql.connector > python3-mysql.connector Might have to try and get these updated in Debian. http://bugs.mysql.com/bug.php?id=71806 Means Django depreciated warnings become fatal errors :-( Have CCed the maintainer (Debian Python Modules Team is uploader). Sandro Tosi, do you have any objections if I package the latest version for Debian? Thanks.
python3-django and mysqldb
According to Django 1.6 documentation: https://docs.djangoproject.com/en/1.6/ref/databases/#python-3 The recommended solution is to use an unofficial fork of mysqldb, such as https://github.com/clelland/MySQL-for-Python-3 According to Django 1.7 documentation, the recommended solution is to use the MySQL Connector/Python: See https://docs.djangoproject.com/en/1.7/ref/databases/#mysql-db-api-drivers Which is already in unstable: python-mysql.connector python3-mysql.connector It looks like these do contain the Django connectors required. So maybe we should update the Django package headers to suggest these instead of mysqldb, as mysqldb development appears to be dead. As far as I can tell this should be supported in Django 1.6 (assuming I am reading a particular line in the documentation correctly). -- Brian May
