Hi, On Tue, 24 Nov 2015, Brian May wrote: > On Mon, Nov 16, 2015 at 02:16:39PM +0100, Raphael Hertzog wrote: > > I forwarded this issue upstream. It looks like the fix should be > > relatively easy and hopefully upsream will pick it up shortly. > > Is this bug really serious? Most people can use Django still without > problem.
Yes, I have a hard time justifying the serious severity... it's probably better at the important severity. At the same time, it clearly blocks the work of Neil so it would be nice to get it fixed sooner rather than later. > Suggest we patch the Debian package from the upstream patch: > https://github.com/django/django/commit/54485557855d58d9a5027511025d5ab22f721c6d > > This has been patched upstream in the 1.9.x tree, not the 1.8.x tree > AFAIK. This is not the fix. This is what creates the problem in Python 2 AFAIK. Did you mean that you just wanted to revert this? I have submitted a first patch on the upstream ticket, it doesn't cover all cases but it will probably fix the issue that Neil is having... so maybe we should go with that patch for now and then demote this to important until upstream has a proper fix. https://code.djangoproject.com/ticket/25761 Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/