Avoided changing raw DeprecationWarning filter behavior

Refs #21188. Now pure Python DeprecationWarning visibility should
be back to Python defaults.

1 files changed, 4 insertions, 2 deletions

diff --git a/django/utils/log.py b/django/utils/log.py
index f319704116..83ba15f52a 100644
--- a/django/utils/log.py
+++ b/django/utils/log.py
@@ -5,6 +5,7 @@ import warnings
 from django.conf import settings
 from django.core import mail
 from django.core.mail import get_connection
+from django.utils.deprecation import RemovedInNextVersionWarning
 from django.utils.module_loading import import_string
 from django.views.debug import ExceptionReporter, get_exception_reporter_filter
 
@@ -68,8 +69,9 @@ def configure_logging(logging_config, logging_settings):
     if not sys.warnoptions:
         # Route warnings through python logging
         logging.captureWarnings(True)
-        # Allow DeprecationWarnings through the warnings filters
-        warnings.simplefilter("default", DeprecationWarning)
+        # RemovedInNextVersionWarning is a subclass of DeprecationWarning which
+        # is hidden by default, hence we force the "default" behavior
+        warnings.simplefilter("default", RemovedInNextVersionWarning)
 
     if logging_config:
          # First find the logging configuration function ...