Changes between Version 4 and Version 5 of LoggingProposal


Ignore:
Timestamp:
10/10/2009 09:48:08 PM (6 years ago)
Author:
simon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • LoggingProposal

    v4 v5  
    99== The Plan ==
    1010
    11 1. DONE: Create a 'django' logger, hooked up to a NullHandler and with propagate=False so all logging is silent by default
    12 2. Start using loggers within Django itself (so far only the SQL logger is DONE, and that implementation could definitely be improved)
    13 3. DONE: Add a --loglevel command line switch to ./manage.py runserver to cause specified handlers to print to the console
    14 4. DONE: Add a mechanism for configuring loggers from Django's settings.py file using a LOGGING setting
    15 5. Figure out how users can get fine-grained control over their loggers by writing regular Python code
     11 1. DONE: Create a 'django' logger, hooked up to a NullHandler and with propagate=False so all logging is silent by default
     12 2. Start using loggers within Django itself (so far only the SQL logger is DONE, and that implementation could definitely be improved)
     13 3. DONE: Add a --loglevel command line switch to ./manage.py runserver to cause specified handlers to print to the console
     14 4. DONE: Add a mechanism for configuring loggers from Django's settings.py file using a LOGGING setting
     15 5. Figure out how users can get fine-grained control over their loggers by writing regular Python code
    1616
    1717Items marked DONE above aren't necessarily of production quality yet, but there's enough working code to see how they would look.
Back to Top