On Thu, Feb 20, 2014 at 9:12 AM, Neil Williams <codeh...@debian.org> wrote: > Package: python-django-auth-openid > Version: 0.5-1 > Severity: important > > I've recently updated a django app (not currently in Debian) to > support django1.6 but the app fails due to the use of django-auth-openid > using a deprecated import:
[snip traceback] > This line needs to be: > > from django.conf.urls import * > > Simple change but django1.6 is the current version in unstable, so it would > be good to get > this fixed. Ya, I've already reported this upstream. [0] Along with with some other issues with Django 1.6 compatibility. The bigger problem is that it is not compatible with the Django 1.6 default JSON_SESSION_SERIALIZER. [1] So even if you fix this, most existing projects using django-openid-auth are still going to be broken with Django 1.6 I was hoping that upstream would have some movement with the issue, especially since Ubuntu 14.04 will be a LTS and Canonical has deployments using it. Unfortunately, that doesn't seem to be happening. I'm debating just making a upload to Debian fixing this and a few other issues with a NEWS entry informing users that they'll have to set SESSION_SERIALIZER to pickle. Though there is a very good reason for the change. [2] It might just be better to find a new openid solution and ask for this to be removed from the archive... Any opinion? I guess I should go ahead and do that. It can always be removed latter, and it is broken right now. [0] https://bugs.launchpad.net/django-openid-auth/+bug/1252866 [1] https://bugs.launchpad.net/django-openid-auth/+bug/1252826 [2] https://docs.djangoproject.com/en/dev/releases/1.6/#default-session-serialization-switched-to-json Thanks, -- Andrew Starr-Bochicchio Ubuntu Developer <https://launchpad.net/~andrewsomething> Debian Developer <http://qa.debian.org/developer.php?login=asb> PGP/GPG Key ID: D53FDCB1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org