A special logging handler and namespace for runserver output

[Valentin Golev]

A special logging handler and namespace for runserver output.

Several related features:

• Ability to add own output into runserver output without using print
• A simple way to do so without knowing a thing about logging module. Like adding this handler as a default handler in generated settings.py
• Ability to silence runserver output
• Ability to redirect runserver output
• Ability to get current runserver output while serving with other methods
• Ability to add more verbose Django's remarks with simple way to shut it up

See also discussion: ​http://groups.google.com/group/django-developers/browse_thread/thread/853706d9543e442c?hl=en

[Carl Meyer]

I'm going to mark this invalid, not because these aren't good thoughts, but because all of these "related features" make it too broad to usefully lump into a single ticket. Tickets need to have a clear and focused description, so that it is clear when they are fixed and can be closed.

It seems to me that the first step (which would make sense as a single ticket) would be to convert runserver's existing output to use logging, maintaining the current behavior by default but making it possible to customize the behavior with logging config. I don't think this will be simple (and will require some design discussion on django-developers to figure out the right approach), but in broad strokes I think it would be a good thing.

Once we see how that pans out, it could possibly serve as the basis for a lot of these "related features," if it doesn't provide them inherently.

If you want to keep track of a broader list of things that would be "nice to have" related to logging, debug output, and runserver, a wiki page is a good place to track the overview of a number of related tickets (or ideas that aren't yet tickets).