#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: Accepted
DiscoverRunner,print,logging,stdout,stderr|
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* stage: Unreviewed => Accepted
Comment:
I think this is a good move, so let's accept the ticket.
> I don't think this ticket is necessarily straightforward. For example, I
think the behavior should be opt-in (at least for now) because callers
might not have logging enabled. I'm not sure yet what the API should be
for opting in though. I'm still thinking about it.
Yes... 🤔 And folks have a hard time getting up and running with logging,
so we need to be conscious of that. Part of it is good documentation.
Thanks for all the work you're doing in this area Chris, and thanks for
wanting to pick this up Daniyal!
--
Ticket URL: <https://code.djangoproject.com/ticket/32552#comment:6>
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.5641f7e7a2e49178856bd2996776022d%40djangoproject.com.
