#20349: Don't load test suite when not testing
--------------------------------------+--------------------
Reporter: CollinAnderson | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Testing framework | Version: 1.5
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+--------------------
I noticed that `django/contrib/auth/hashers.py` is loading the
`settings_changed` signal from the test suite. This ends up also loading
the whole test suite in addition.
All of the other code that handles the `settings_changed` signal is kept
inside the test suite itself. I assume this code is kept out of the test
suite because of the "core shouldn't be aware of contrib" rule. Seems to
me it's more important to avoid unnecessarily loading the test suite on a
production website.
Yes, I realize this is picky, but we're perfectionists, right?
--
Ticket URL: <https://code.djangoproject.com/ticket/20349>
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].
For more options, visit https://groups.google.com/groups/opt_out.
