From eb286aa22f2a83a091b856ab2ecda1bded4203e3 Mon Sep 17 00:00:00 2001 From: Claude Paroz Date: Wed, 6 Jun 2012 10:53:16 +0200 Subject: Delayed encoding of password and salt in password checking. Applied the rule that string encoding should happen as late as possible. This is also a preparation for Python 3 compatibility. --- docs/releases/1.5.txt | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'docs') diff --git a/docs/releases/1.5.txt b/docs/releases/1.5.txt index 0d86a52670..696f332285 100644 --- a/docs/releases/1.5.txt +++ b/docs/releases/1.5.txt @@ -128,6 +128,15 @@ If you were using the ``data`` parameter in a PUT request without a ``content_type``, you must encode your data before passing it to the test client and set the ``content_type`` argument. +String types of hasher method parameters +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +If you have written a :ref:`custom password hasher `, +your ``encode()``, ``verify()`` or ``safe_summary()`` methods should accept +Unicode parameters (``password``, ``salt`` or ``encoded``). If any of the +hashing methods need byte strings, you can use the +:func:`~django.utils.encoding.smart_str` utility to encode the strings. + Features deprecated in 1.5 ========================== -- cgit v1.3