Django-otp

Latest version: v1.5.4

Safety actively analyzes 701836 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 10 of 12

0.3.2

--------------------------------------

- Stop importing models into the root of the package.

- Use ModelAdmin.raw_id_fields for foreign keys to users.

- General cleanup and compatibility with Django 1.9a1.

0.3.1

-----------------------------------

- Add support for the new app registry, when available.

- Add Django 1.8 to the test matrix and fix a few test bugs.

0.3.0

-----------------------------------------------------

- All plugins now have both Django and South migrations. Please see the `upgrade
notes`_ for details on upgrading from previous versions.

.. _upgrade notes: https://pythonhosted.org/django-otp/overview.html#upgrading

0.2.7

---------------------------------------------------------------

- Updated the otp_totp South migrations to support custom user models. Thanks to
https://bitbucket.org/robirichter.


v0.2.6 - April 18, 2014 - Fix for Python 3.2 with South
-------------------------------------------------------

- Removed South-generated unicode string literals.

0.2.4

-------------------------------------------------------------

- Per the RFC, :class:`~django_otp.plugins.otp_totp.models.TOTPDevice` will no
longer verify the same token twice.

- Cosmetic fixes to the admin login form on Django 1.6.

.. warning::

This includes a model change in TOTPDevice. If you are upgrading and your
project uses South, you should first convert it to South with ``manage
migrate otp_totp 0001 --fake``. If you're not using South, you will need to
generate and run the appropriate SQL manually.

0.2.3

-------------------------------------

- OTPMiddleware no longer interferes with pickling request.user.

Page 10 of 12

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.