#18243: Management shell should make it easy to force LOGGING_CONFIG=None
-------------------------------------+-------------------------------------
Reporter: ncoghlan@… | Owner: nobody
Type: Uncategorized | Status: new
Component: Core (Management | Version: 1.3
commands) | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by vsajip):
I'm not a core Django committer, but as the maintainer of logging I do
agree with Nick that doing logging configuration as a side-effect of
import is not good. It's fine to provide a convenience API (ideally, an
idempotent one) to configure logging, and to document that; that API can
be called either by client code or by Django code in code paths where
Django is being run as a management script. The problem with assuming
you'll always want to configure logging automagically is that you can't be
sure how people want to use Django, which might not be in a conventional
way. For example, I've seen people trying to use just the ORM part. And
since Django is used as part of a bigger system, that system's developers
might want to choose exactly when to configure logging. It should always
be under the control of the application (as opposed to library or
framework) developer.
--
Ticket URL: <https://code.djangoproject.com/ticket/18243#comment:4>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
