execute_manager removed in Django 1.6

This now causes FTBFS in Ubuntu, see https://launchpadlibrarian.net/164425402/buildlog_ubuntu-trusty-i386.django-openid-auth_0.5-1_FAILEDTOBUILD.txt.gz

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...

This bug was fixed in the package django-openid-auth - 0.5-2

---------------
django-openid-auth (0.5-2) unstable; urgency=medium

  * debian/patches/django1.6compat.patch: Fix compatibility
    issues with Django 1.6 (Closes: #729828, 739617)
    (LP: #1252866, #1252445).
  * Add debian/NEW entry describing the situation with
    the new Django session serializer.
  * Bump Standards-Version to 3.9.5, no changes needed.
  * Transition from python-support to dh_python2.

 -- Andrew Starr-Bochicchio <email address hidden> Sat, 22 Feb 2014 13:00:49 -0500