--
Ticket URL: <https://code.djangoproject.com/ticket/28660>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* owner: nobody => Uman Shahzad
* status: new => assigned
--
Ticket URL: <https://code.djangoproject.com/ticket/28660#comment:1>
* has_patch: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/28660#comment:2>
Comment (by Aymeric Augustin):
It is documented here:
https://docs.djangoproject.com/en/1.11/topics/auth/passwords/#included-
hashers
I'm not seeing a pressing reason to remove this hasher, which may be used
for compatibility with existing password databases.
If there's a decision to remove it, that should go through a deprecation
path.
--
Ticket URL: <https://code.djangoproject.com/ticket/28660#comment:3>
* status: assigned => closed
* resolution: => wontfix
Comment:
I agree -- unless a discussion on the DevelopersMailingList yields a
consensus that the original use case in #3316 in obsolete, this hasher
doesn't have much maintenance cost and it's better for there to be a
canonical implementation rather than requiring users to implement it
themselves.
--
Ticket URL: <https://code.djangoproject.com/ticket/28660#comment:4>