Skip to content

Conversation

collinanderson
Copy link
Contributor

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?

https://code.djangoproject.com/ticket/20349

@ramiro
Copy link
Member

ramiro commented May 16, 2013

I don't see how the code could actually load the test suite. Maybe you meant the django.test package?

@collinanderson
Copy link
Contributor Author

ohh. yes. the "test" package. not quite as bad, though it's still a large amount of code that is unnecessarily loaded.

@aaugustin
Copy link
Member

As explained by Carl in the ticket this PR can't work.

@aaugustin aaugustin closed this May 19, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants