Note that LP: #1252826 is really the bigger problem. Even if you fix the test failure using my branch, 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 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 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. It might just be better to find a new openid solution and ask for this to be removed from Trusty...