#32552: Change DiscoverRunner to use a logger instead of print
-------------------------------------+-------------------------------------
Reporter: Chris Jerdonek | Owner: nobody
Type: New feature | Status: new
Component: Testing framework | Version: 4.0
Severity: Normal | Resolution:
Keywords: | Triage Stage:
DiscoverRunner,print,logging,stdout,stderr| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Chris Jerdonek):
I'll note that one thing this would help with is when testing
`DiscoverRunner`. Currently, testing some `DiscoverRunner` methods results
in undesired console output. If a logger was used instead of printing,
then the test framework could take care of this without any extra work.
Using a logger would also make it easier to test that certain messages are
being emitted, because the testing framework's logging assertions could be
used.
--
Ticket URL: <https://code.djangoproject.com/ticket/32552#comment:1>
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/067.c6cb609f775dc87be5b6276447d2b84c%40djangoproject.com.
