We've made the first release on the way to Django's next major release,
Django 1.11! With two and a half months until the scheduled final release,
we'll need timely testing from the community to ensure an on-time and
stable release. Check out the blog post:
https://www.djangoproject.com/weblog/
I've reviewed and merged as much as I can (thank you to everyone who
helped!) and plan to create the stable/1.11.x branch and issue the alpha
release in approximately 7 hours.
On Monday, December 26, 2016 at 1:17:01 PM UTC-5, Tom Christie wrote:
>
> >
> this feature https://github.com/django/dj
I propose to tentatively target Python 3.5+ for Django 2.0 but not to
remove the current workarounds for Python 3.4 at this time. Shortly before
the alpha for Django 2.0, an interested person can look into how much work
is required to fix any test failures on Python 3.4 and we'll make a
decisio
Also django-two-factor, which builds on django-otp and provides all
extra bits you might need, eg setup views, QR code generation for
device registration, login wizards etc supporting HOTP/TOTP, static
tokens, Yubikey and SMS.
https://markusholtermann.eu/2016/09/2-factor-authentication-in-django/