#18405: Delay string encoding in contrib.auth.hashers
------------------------------------------------+-------------------------
Reporter: claudep | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: contrib.auth | Version: master
Severity: Normal | Keywords: python3
Triage Stage: Ready for checkin | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+-------------------------
As a preparation to switch to more Unicode strings on the road to Python
3, I suggest to encode strings only at the exact moment that we need
encoded strings. In contrib.auth.hashers (see patch), this might produce a
slightly backwards-incompatible behavior, but should affect very few users
(only those having written a custom password hasher and if this hasher
does not support Unicode strings).
I'm setting this as RFC, as I'm rather confident about it (all tests pass)
and I'm about to push it. But I'd like to offer the time for a quick
review or a stop if any strong argument would appear against it.
--
Ticket URL: <https://code.djangoproject.com/ticket/18405>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
