Raphael said he is not subscribed, so I have sent this to him.
On 07/23/2014 08:27 AM, Brian May wrote:
> Hello,
>
> Thanks for you work. I very much agree, would really like to see Django
> 1.7 in Jessie, even if it does break some things along the way.
I don't agree with the last bit of your sentence.
Django 1.7 final isn't even released upstream, and therefore, downstream
projects didn't even try to run against it. There *will* be issues we
will have to deal with. 85 packages is quite something. I'm ok, and even
welcome to *try* to make it before Jessie, though it is my view that
it's unreasonable to rush without taking care of possible breaking.
So, let's try to do it as much as possible. But if it isn't, and we have
a non-negligeable amount of problems, and we can't make it before the
freeze date, let's have no hard feeling.
FYI, I'm trying to deal with python-memcache support for Python 3.4.
Until that one is fixed, I wont be able to add support for Python 3 in
keystoneclient, and therefore *a lot* of other packages will have no
Python 3 support. I've tried to forward port a patch from
python3-memcached, though it's still not ready, and unit tests are
failing. Julien Danjou (eg: acid@d.o) wrote to me he'll try to find time
to help. I really hope this one issue will be fixed soon, so that I can
work on adding Python 3 everywhere possible in OpenStack, though right
now it's a major blocker. I also hope we can upstream Python3 support
for memcached, as the python3-memcached fork has been a major waste IMO.
Cheers,
Thomas
--
To UNSUBSCRIBE, email to debian-python-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: [🔎] 53DDB6D9.2020806@debian.org" target="_blank">https://lists.debian.org/[🔎] 53DDB6D9.2020806@debian.org