#20917: Change the password hashers when testing
-------------------------------------+-------------------------------------
Reporter: mjtamlyn | Owner:
Type: New feature | ashchristopher
Component: Testing framework | Status: assigned
Severity: Normal | Version: master
Keywords: | Resolution:
Has patch: 0 | Triage Stage: Accepted
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by jcd):
Apologies. Anonymous above (comment:5) is me. Is there a way to check
if the hasher has been manually set, and use that if so, but to have it
default to something fast if no hasher has been specified? I think a fast
test suite is something we want people to be able to use by default. My
concern is that requiring TEST_PASSWORD_HASHER to be set to get fast tests
doesn't solve the problem, it just moves the workaround from supplying a
separate settings file to supplying an extra setting. It's better, but
we're still leaving new users with slow tests.
Or, if the solution requires TEST_PASSWORD_HASHER to be set, include it in
the default settings file created by makeproject.
--
Ticket URL: <https://code.djangoproject.com/ticket/20917#comment:8>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.dcb8eaa82b475e57158ac019f397c57e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
