Re: Django 1.7 preparations

To: Raphael Hertzog <hertzog@debian.org>, debian-python <debian-python@lists.debian.org>

Subject: Re: Django 1.7 preparations

From: Brian May <brian@microcomaustralia.com.au>

Date: Wed, 3 Sep 2014 09:04:09 +1000

Message-id: <[🔎] CAA0ZO6AWjcGpWT6Pew8XsqJwv0mv1XycQ-Xa8t3Jc3hURs+_qw@mail.gmail.com>

In-reply-to: <CAA0ZO6B=PQVOVtU8b0=w0D4KCfXzYmL=hV5NtxFLtLZjtQk_PQ@mail.gmail.com>

References: <20140807214803.GB11746@x230-buxy.home.ouaza.com> <CAA0ZO6B=PQVOVtU8b0=w0D4KCfXzYmL=hV5NtxFLtLZjtQk_PQ@mail.gmail.com>

On 22 August 2014 09:49, Brian May <brian@microcomaustralia.com.au> wrote:

I think the following bug I just noticed is significant. Unless fixed, it means that after Django 1.7 is released Debian won't have a Mysql library for it that works with Python3.

https://bugs.debian.org/758844
http://bugs.mysql.com/bug.php?id=72542

Seems like it was fixed upstream, but they didn't bother to update that bug report, so I was in the dark.

http://dev.mysql.com/doc/relnotes/connector-python/en/news-1-2-3.html

--
Brian May <brian@microcomaustralia.com.au>

Reply to: