#17825: ImproperlyConfigured: You must enable
'django.core.context_processors.request' in TEMPLATE_CONTEXT_PROCESSORS
-----------------------------------+--------------------------------------
Reporter: EvoTech | Owner: nobody
Type: Bug | Status: new
Component: Testing framework | Version: 1.4-beta-1
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------------------------
Comment (by carljm):
Oh, I just realized that r17598 itself fixed a release-blocking regression
(#16366).
The more we have to isolate contrib-app tests from the project settings,
the less justification there is for even having those tests run in
anyone's project. Until we achieve perfect isolation, we'll keep getting
reports of failures due to differences in someone's setup. Once we achieve
perfect isolation, having those tests run by default just uselessly slows
down people's test suites with extra tests that will never fail (unless
they are mucking in contrib.auth's own codebase).
It's possible there could be a few integration tests that are not isolated
and must pass in any project where contrib.auth is functioning, but I
doubt that it is even possible to write such tests and have them still be
useful, given all the possible customizations of contrib.auth in a given
project. Such integration tests should be provided by the project, which
knows how their integration works, not by contrib.auth.
So I think the real fix to this and #16366 is just to place contrib.auth's
tests in Django's own test suite instead, or in a submodule of
contrib.auth such that they only run if you place "contrib.auth.tests" in
the installed apps.
--
Ticket URL: <https://code.djangoproject.com/ticket/17825#comment:2>
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.
