#33058: Use DiscoverRunner's logger for logging when running checks
-------------------------------------+-------------------------------------
Reporter: Chris | Owner: Chris Jerdonek
Jerdonek |
Type: | Status: assigned
Cleanup/optimization |
Component: Testing | Version: dev
framework |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Currently, when a logger is passed to `DiscoverRunner`, there is at least
one case where `DiscoverRunner`'s logger isn't used for logging log-like
messages. This is when `DiscoverRunner` runs the `check` command (code
[https://github.com/django/django/blob/55cf9e93b5e5bdf19bedeb1d900ee8a83f8489fb/django/test/runner.py#L847
here]) and displays a message like the "System check identified no issues
...."
While there is some overlap with ticket #21429 (which is about logging for
''all'' commands), I think this ticket can be kept separate because it can
be done independently, and in particular either before or after that
ticket is complete.
I do have at least one idea of how this ticket can be addressed pretty
simply, and in a way that would help make tangible forward progress on
#21429. I can add a comment to that ticket explaining the approach in
order to keep followers of that ticket in the loop.
--
Ticket URL: <https://code.djangoproject.com/ticket/33058>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.d06aa82edeac96aa68fa0d45a4304d26%40djangoproject.com.
