#27931: Clarify the meaning of "django catch-all logger"
-------------------------------------+-------------------------------------
Reporter: Jesse | Owner: Tim
Type: | Graham <timograham@…>
Cleanup/optimization | Status: closed
Component: Documentation | Version: 1.10
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* owner: (none) => Tim Graham <timograham@…>
* resolution: => fixed
Comment:
In [changeset:"f21915bb3ad73001b7d987332b2b4a0ae4ec288d" f21915bb]:
{{{
#!CommitTicketReference repository=""
revision="f21915bb3ad73001b7d987332b2b4a0ae4ec288d"
Fixed #27931 -- Clarified the meaning of "django catch-all logger."
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27931#comment:10>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.982ce666b86ed16c314b98d8b0c0250f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
