FWI a new ticket[1] with what looks like a sane implementation to add this
level of logging to the runserver command has been created.
I'll make sure to copy all the concerns raised by Russ over there and you
might want to chime in the review process.
Simon
[1] https://code.djangoproject.com/t
On Thu, May 29, 2014 at 3:40 AM, Russell Keith-Magee <
russ...@keith-magee.com> wrote:
> However, there's a cost - we'd be adding the requirement for a logging
> configuration for something that is only ever used during development. So
> we'd end up complicating the process of deploying the devser
Today I learned that the devserver messages are supposed to be in color.
Having all output from Django controlled by logging would be a nice
improvement.
Regards,
Michael Manfre
On Wed, May 28, 2014 at 9:40 PM, Russell Keith-Magee <
russ...@keith-magee.com> wrote:
>
> On Wed, May 28, 2014 at 3
On Wed, May 28, 2014 at 3:35 AM, Martín Massera wrote:
> Hi sometimes when you are developing you get so much output in the
> console, especially when you have many medias on the page. It would be nice
> to use the logging system to remove those messages, but right now stderr is
> being used.
>
>
Hi sometimes when you are developing you get so much output in the console,
especially when you have many medias on the page. It would be nice to use
the logging system to remove those messages, but right now stderr is being
used.
Using the logging system for choosing whether we want to see thi