Hi, On Fri, 31 Aug 2012, Winfried Tilanus wrote: > So lets get back to the original issue: the changelog mentions fixed > compatibility issues with Django 1.4: > https://bitbucket.org/ubernostrum/django-registration/src/2d6fcc0c55d0/CHANGELOG > > It is for sure referring to this commit: > https://bitbucket.org/ubernostrum/django-registration/changeset/b79f9f2cf3c9f246d68a0e5d3b9e75ab0c1b20c6 > > I have seen one bug report about this causing problems: > http://spottedsun.com/django-registration-activation-error-for-django-1-4/
Thanks, this makes sense since the Django 1.4 changed the model for date and time to include a timezone. So that's a severe regression caused by Django 1.4 (failing while checking if the activation key expired or not). https://docs.djangoproject.com/en/1.4/releases/1.4/#support-for-time-zones https://docs.djangoproject.com/en/1.4/topics/i18n/timezones/#time-zones-migration-guide Cheers, -- Raphaël Hertzog ◈ Debian Developer Get the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
