#25684: Runserver doesn't use `LOGGING` configuration
-----------------------------------+------------------------------------
Reporter: fcurella | Owner: fcurella
Type: New feature | Status: assigned
Component: Error reporting | Version: master
Severity: Normal | Resolution:
Keywords: runserver logging | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-----------------------------------+------------------------------------
Comment (by andreif):
Wouldn't it feel strange if the logger has `runserver` in it's name? As I
see it, user starts the server using `runserver` command. The logging is
done by the server, not the command which started the server. The server
could be started via something else, not related to `runserver` command.
So `django.server` would fit better from my point of view and also
looks/sounds better.
`django.request` deals with application level logging so using it (or its
sublogger) for the server which runs the application is not what one would
expect.
Personally, I don't see any disadvantage of `django.server` but since I am
(seemingly) the only one advocating for it, I wonder why one would not
prefer it?
--
Ticket URL: <https://code.djangoproject.com/ticket/25684#comment:29>
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/066.552a99967880faabc4e0c7a0591b27d4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
