#25684: Runserver doesn't use `LOGGING` configuration
---------------------------------+--------------------------------------
     Reporter:  fcurella         |                    Owner:
         Type:  New feature      |                   Status:  new
    Component:  Error reporting  |                  Version:  1.8
     Severity:  Normal           |               Resolution:
     Keywords:                   |             Triage Stage:  Unreviewed
    Has patch:  0                |      Needs documentation:  0
  Needs tests:  0                |  Patch needs improvement:  0
Easy pickings:  0                |                    UI/UX:  0
---------------------------------+--------------------------------------
Changes (by fcurella):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Old description:

> this is slightly related to https://code.djangoproject.com/ticket/25523
>
> All output in ``core.servers.basehttp`` (and possibly ``fastcgi`` - I
> haven't checked that yet) uses ``sys.stderr.write``, bypassing the
> logging subsystem.
>
> In order to have it use the ``LOGGING`` settings, I can see 3 options:
>
> a) make it always use ``logger.info(msg)`` and change the default
> `LOGGING` settings appropriately
> b) make it always use both ``sys.stdout.write`` and ``logger.info``
> c) add an option to runserver to switch behaviour
>
> I'm willing to work on the patch (in fact, I have option 2) already
> working), I just need to know if this is something we want and what
> direction we want to go.

New description:

 this is slightly related to https://code.djangoproject.com/ticket/25523

 All output in `core.servers.basehttp` (and possibly `fastcgi` - I haven't
 checked that yet) uses ``sys.stderr.write``, bypassing the logging
 subsystem.

 In order to have it use the `LOGGING` settings, I can see 3 options:

 a) make it always use `logger.info(msg)` and change the default `LOGGING`
 settings appropriately
 b) make it always use both `sys.stdout.write` and ``logger.info`
 c) add an option to runserver to switch behaviour

 I'm willing to work on the patch (in fact, I have option 2) already
 working), I just need to know if this is something we want and what
 direction we want to go.

--

--
Ticket URL: <https://code.djangoproject.com/ticket/25684#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 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.a7a3086d4009b099590ac0c6c27e8a09%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to