From b2d78939d171f12ae7baaf0a2fa5a29b43bb2e47 Mon Sep 17 00:00:00 2001 From: Claude Paroz Date: Wed, 1 Jan 2014 22:55:50 +0100 Subject: Prevented calling setup() inside catch_warnings When django.setup() (and then configure_logging) is called inside catch_warnings, logging setup is negatively affected (notably warnings.showwarning definition). --- tests/logging_tests/tests.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'tests/logging_tests') diff --git a/tests/logging_tests/tests.py b/tests/logging_tests/tests.py index f020bfddef..5b536f9e82 100644 --- a/tests/logging_tests/tests.py +++ b/tests/logging_tests/tests.py @@ -91,8 +91,8 @@ class WarningLoggerTests(TestCase): """ def setUp(self): # If tests are invoke with "-Wall" (or any -W flag actually) then - # warning logging gets disabled (see django/conf/__init__.py). However, - # these tests expect warnings to be logged, so manually force warnings + # warning logging gets disabled (see configure_logging in django/utils/log.py). + # However, these tests expect warnings to be logged, so manually force warnings # to the logs. Use getattr() here because the logging capture state is # undocumented and (I assume) brittle. self._old_capture_state = bool(getattr(logging, '_warnings_showwarning', False)) -- cgit v1.3