I just upgraded to Django 3.2.15 from 3.1.14 and the test suite has become very “chatty”, outputting to stdout multiple exceptions (custom ones, HTTP, Django-specific exceptions). I am not sure what was changed in Django 3.2 that causes this verbose output – this change is not documented in the release notes. Previously I had a similar issue with the *geocoder* library polluting the output of the tests and I managed to resolve it by adding a logging.NullHandler() to geocoder’s logger. This does not seem to work anymore and also geocoder’s exceptions have returned (these are expected exceptions, since my tests check that the code properly handles failed connections to the geocoding services).
Can someone please point me to the change in Django that started causing this verbose output since version 3.2, and what would be the most suitable approach to remove it? (we are not using pytest or tox, just Django’s built-in test runner). -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/f9f3ce6c-880c-4e11-b8c0-8ad123e9d1fcn%40googlegroups.com.
