Re: [Django] #12012: Integration with the Python standard library logging module

[Django]

#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  closed  | Milestone:  1.3   
 Component:  Core framework  |   Version:  SVN   
Resolution:  fixed   |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by intgr):

 @anonymous: Did you consider database transactions?

 If you're using database transactions in your app, the logging will seem
 to be working fine, until you actually reach an error... The errors will
 be successfully written out to your log table, but then comes along your
 transaction manager and rolls everything back due to the failed
 transaction. ;)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12012: Integration with the Python standard library logging module

[Django]

#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:  1.3   
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by tvon):

 * cc: tomv...@gmail.com (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12012: Integration with the Python standard library logging module

[Django]

#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:  1.3   
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

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

Comment:

 @anon - Nothing in particular; if you want to log to database, that's
 certainly an option with an appropriate handler.

 My only concern would be the extra database load that this logging
 technique would introduce, but that isn't something that you can declare
 as universally bad; it entirely depends on your load pattern and the
 amount of logging you intend to do.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12012: Integration with the Python standard library logging module

[Django]

#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:  1.3   
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Comment (by anonymous):

 I've made a working logger by just using a simple encapsulation of
 database table with two main field: level and text, this has the advantage
 of being instantly available in Django admin.  What am I missing with this
 approach?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12012: Integration with the Python standard library logging module

[Django]

#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:  1.3   
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Changes (by alexkoshelev):

 * cc: alexkoshelev (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12012: Integration with the Python standard library logging module

[Django]

#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:  1.3   
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Comment (by vsajip):

 Updated code on Launchpad to bring up to date with Django trunk (r13679)
 and to deal with points raised by Remi Broemeling. See

 http://bazaar.launchpad.net/~vinay-sajip/django/logging/

 for the latest version.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12012: Integration with the Python standard library logging module

[Django]

#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:  1.3   
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Comment (by remibroemeling):

 Sorry for the double post, but possibly the .setLevel() call should be
 moved to take place under "if len(logger.handlers) == 0:" as well.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12012: Integration with the Python standard library logging module

[Django]

#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:  1.3   
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Comment (by remibroemeling):

 A comment on http://bazaar.launchpad.net/~vinay-
 sajip/django/logging/revision/56 , specifically the code:

 {{{
 if len(logger.handlers) == 0:
 logger.addHandler(NullHandler())
 logger.propagate = False
 }}}

 This will set the 'django' logger not to propagate, even if the user
 (previous to the inclusion of django) has it configured TO propagate.
 Changing it to:

 {{{
 if len(logger.handlers) == 0:
 logger.addHandler(NullHandler())
 logger.propagate = False
 }}}

 ... would have the same effect in the case of Django starting up when
 logging hasn't been configured, but wouldn't alter an existing logging
 setup in a way that the user wouldn't expect.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12012: Integration with the Python standard library logging module

[Django]

#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:  1.3   
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Changes (by remibroemeling):

 * cc: remibroemeling (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12012: Integration with the Python standard library logging module

[Django]

#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:  1.3   
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Changes (by vinay_sa...@yahoo.co.uk):

  * milestone:  => 1.3

Comment:

 I've added a Launchpad branch which is an up-to-date branch of Django
 trunk (as at today - 13 May 2010), with updated logging functionality
 (including a copy of dictConfig, from my project of the same name which is
 a standalone version of the new PEP 391 logging configuration
 functionality, usable with Python 2.4, 2.5 and 2.6). I've inserted some
 logging statements in app loading, SQL execution and request handling
 (including handling of uncaught and other exceptions).

 There's also an example project which uses the Django logging API to
 configure logging in settings.py, via PEP 391-compatible configuration
 dictionary (the initialisation code is only called once, even though
 settings.py is imported at least twice).

 Bazaar branch for the version of Django with logging enabled:
 https://code.launchpad.net/~vinay-sajip/django/logging
 Bazaar branch for test project, which shows how logging can be configured:
 https://code.launchpad.net/~vinay-sajip/+junk/django-logtest

 The test app is set up to log to /tmp/logtest.log (which isn't spammed
 with SQL logging) and /tmp/logtest-sql.log (which contains the SQL
 statements executed).

 Basic diffs to show what was added:

 http://bazaar.launchpad.net/~vinay-sajip/django/logging/revision/53 -
 Added callback hooks
 http://bazaar.launchpad.net/~vinay-sajip/django/logging/revision/55 -
 Added log module reference
 http://bazaar.launchpad.net/~vinay-sajip/django/logging/revision/56 -
 Added log module itself
 http://bazaar.launchpad.net/~vinay-sajip/django/logging/revision/55 -
 Removed log module reference (as not needed)
 http://bazaar.launchpad.net/~vinay-sajip/django/logging/revision/61 -
 Added dictconfig.py and changed code to use it
 http://bazaar.launchpad.net/~vinay-sajip/django/logging/revision/62 -
 Added useful default to configuration
 http://bazaar.launchpad.net/~vinay-sajip/django/logging/revision/63 -
 Added logging to app loading
 http://bazaar.launchpad.net/~vinay-sajip/django/logging/revision/65 -
 Added logging for SQL and uncaught exceptions in request handling
 http://bazaar.launchpad.net/~vinay-sajip/django/logging/revision/67 -
 Added some more logging to request handling code


 Your feedback will be appreciated, especially in terms of other parts of
 Django that you think would benefit particularly from having logging
 added.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12012: Integration with the Python standard library logging module

[Django]

#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Changes (by gciotta):

 * cc: gcio...@gmail.com (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12012: Integration with the Python standard library logging module

[Django]

#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Changes (by russellm):

  * stage:  Unreviewed => Accepted

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12012: Integration with the Python standard library logging module

[Django]

#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Changes (by anonymous):

 * cc: medos...@gmail.com (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12012: Integration with the Python standard library logging module

[Django]

#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Changes (by offbytwo):

 * cc: cstejer...@gmail.com (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

--

You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12012: Integration with the Python standard library logging module

[Django]

#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Comment (by anonymous):

 See Simon's experimental branch on this feature
 [http://github.com/simonw/django/tree/logging on github] and this
 [http://groups.google.com/group/django-
 developers/browse_thread/thread/8551ecdb7412ab22/02eda751f351d7bd djd
 thread]

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

--

You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12012: Integration with the Python standard library logging module

[Django]

#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Changes (by shanx):

 * cc: re...@maykinmedia.nl (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

--

You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=.

Re: [Django] #12012: Integration with the Python standard library logging module

[Django]

#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Changes (by robhudson):

 * cc: r...@cogit8.org (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #12012: Integration with the Python standard library logging module

[Django]

#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Comment (by vsajip):

 I've proposed the detail of a dictionary schema for Python logging
 configuration on python-dev in [http://mail.python.org/pipermail/python-
 dev/2009-October/093062.html this post]. An example configuration in YAML
 format would be:
 {{{
 formatters:
   brief:
 format: '%(levelname)-8s: %(name)-15s: %(message)s'
   precise:
 format: '%(asctime)s %(name)-15s %(levelname)-8s %(message)s'
 datefmt: '%Y-%m-%d %H:%M:%S'
 filters:
   allow_foo:
 name: foo
 handlers:
   console:
 class : logging.StreamHandler
 formatter: brief
 level   : INFO
 stream  : ext://sys.stdout
 filters: [allow_foo]
   file:
 class : logging.handlers.RotatingFileHandler
 formatter: precise
 filename: logconfig.log
 maxBytes: 1024
 backupCount: 3
   debugfile:
 class : logging.FileHandler
 formatter: precise
 filename: logconfig-detail.log
 mode: a
   email:
 class: logging.handlers.SMTPHandler
 mailhost: localhost
 fromaddr: my_app at domain.tld
 toaddrs:
   - support_team at domain.tld
   - dev_team at domain.tld
 subject: Houston, we have a problem.
 loggers:
   foo:
 level : ERROR
 handlers: [debugfile]
   spam:
 level : CRITICAL
 handlers: [debugfile]
 propagate: no
   bar.baz:
 level: WARNING
 root:
   level : DEBUG
   handlers  : [console, file]

 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #12012: Integration with the Python standard library logging module

[Django]

#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Comment (by vsajip):

 Result of running {{{./manage.py validate}}} with patch in
 12012-r11624.diff and attached settings.py:

 {{{
 2009-10-15 14:58:31,772 INFO logtest   Adding listener for
 class_prepared...
 2009-10-15 14:58:31,803 INFO logtest   class_prepared listener
 called: ContentType
 2009-10-15 14:58:31,805 INFO logtest   class_prepared listener
 called: Permission
 2009-10-15 14:58:31,807 INFO logtest   class_prepared listener
 called: Group
 2009-10-15 14:58:31,810 INFO logtest   class_prepared listener
 called: User
 2009-10-15 14:58:31,813 INFO logtest   class_prepared listener
 called: Message
 2009-10-15 14:58:31,843 INFO logtest   class_prepared listener
 called: Session
 2009-10-15 14:58:31,864 INFO logtest   class_prepared listener
 called: Site
 2009-10-15 14:58:31,916 INFO logtest   ORM works: all users: vinay
 (Vinay Sajip)
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #12012: Integration with the Python standard library logging module

[Django]

#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Comment (by vsajip):

 As per [http://groups.google.com/group/django-
 developers/msg/90b81d9f927d0bf0 this thread on django-developers]

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #12012: Integration with the Python standard library logging module

[Django]

#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Changes (by isagalaev):

 * cc: man...@softwaremaniacs.org (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #12012: Integration with the Python standard library logging module

[Django]

#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Comment (by vsajip):

 No, you're right about the best way to achieve what you want - i.e. by
 adding the {{{NullHandler}}} and setting propagate to False on the
 "django" logger, you will indeed ensure that any thing logged to
 "django.*" will disappear into the ether. That'll be fine from a backward
 compatibility point of view - users who have old settings files shouldn't
 see any unexpected logging messages.

 The other question is what different modes of initialisation of logging
 might be wanted by different users. If a user wants Django to
 automatically configure logging for them, they can define a dict bound to
 LOGGING in settings.py. This covers the simplest use case - users don't
 need to do anything else. About the schema for the dict, it would be nice
 if we could align the schema with what I'm proposing on python-dev,
 linked-to above (the schema ''is'' different to what Ivan Sagalaev
 suggested on the django-developers thread, but then it has to cover
 functionality of the logging module such as shared handlers, filters,
 formatters etc. which wasn't covered by Ivan's overview, but will be
 needed in certain cases).

 In a more complex use case, say the user wants to set up logging using
 their own code, but this needs to be done as early as possible and be
 called just once. For this, I suggested a callback mechanism
 [http://groups.google.com/group/django-
 
developers/tree/browse_frm/thread/43ad9bd9337cfb5c/56ae96ba80604e19#doc_c600420b7b093f51
 here] on your thread about "Best place for code that processes stuff from
 settings.py once". There, the user could define callbacks for logging or
 anything else which needs to be done just once. Their logging setup
 callback can use any mechanism to configure logging, e.g. programmatically
 using the logging getLogger/addHandler APIs or via loading a dict from
 YAML or JSON or just invoking the dict config mechanism using a dict
 obtained from some other source - including a literal dict in settings.py
 not called LOGGING ;-)

 One more point about handlers. Because propagate is set to False for the
 "django" logger, in order for users to see django events, they will
 explicitly have to add appropriate handlers to the "django" logger. These
 can be the same handlers as they e.g. attach to the root logger, or
 completely different handlers.

 A fairly common usage pattern is to attach console, file handlers to the
 root logger and nowhere else (but that wouldn't work for Django events, as
 I've explained above). Another common pattern is to attach console and
 file handlers to the root, and additional handlers (e.g. SMTP or file
 handlers pointing to files which just store errors) for particular
 severities (e.g. ERROR or CRITICAL) and/or particular areas of the
 application.

 Of course, knowledgeable users can, if they wish, set the "django"
 logger's propagate flag to True in their logging setup code, which means
 that they then don't need to attach handlers specifically to the "django"
 logger, as events will propagate up to the root logger.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #12012: Integration with the Python standard library logging module

[Django]

#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Comment (by simon):

 I might be going about the initialisation the wrong way then. Here's what
 I want to achieve: without the user needing to do anything at all
 (including modifying a settings.py created before logging was added to
 Django) I want ALL messages to any logger beneath "django" to be silently
 swallowed, no matter what the severity. My understanding is that the
 correct way to do this is to hook up a NullHandler and set "propogate =
 False" on the "django" logger as early as possible. Is there a better way
 of achieving that?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #12012: Integration with the Python standard library logging module

[Django]

#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Comment (by vsajip):

 Comments on 12012-r11603.diff:

 Re. the change in {{{conf/__init__.py}}}:

 I know there's an open issue about where to place setup code in Django to
 run once only, so I assume this placement of the logging configuration
 code is just temporary because no better mechanism exists? As a user, I
 would prefer to control exactly when and how logging gets set up, and not
 to have it done automagically for me. If you feel that automagic
 configuration is wanted by the majority of users, you can still have an
 additional setting called e.g. AUTOLOG, set by default to True if you
 want, which does the logging setup automatically when true but can be
 overridden when more precise control is wanted. In fact if more
 granularity over logging settings is wanted, you could have a settings
 dict LOGGING_CONFIG {  "enabled": True, "automatic": True } etc.

 Re. the change in {{{db/backends/__init__.py}}}:

 You might want to control via settings.py whether a
 {{{CursorLoggingWrapper}}} is returned rather than a plain cursor. There
 might be some petrol-heads for whom speed is paramount ;-)

 Re. the change in {{{"/dev/null"}}}, presumably this is your new
 {{{django.utils.log}}}:

 I've proposed on python-dev a change to Python logging to add a
 dictConfig() function to the {{{logging.config}}} module. The start of the
 thread is [http://mail.python.org/pipermail/python-
 dev/2009-October/thread.html#92695 here] (though some of the posts don't
 appear in this thread because of broken email clients) and the draft of
 the schema I'm proposing is [http://mail.python.org/pipermail/python-
 dev/2009-October/092782.html here]. It would be good if we could align the
 schemata for the {{{LOGGING}}} dict.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #12012: Integration with the Python standard library logging module

[Django]

#12012: Integration with the Python standard library logging module
-+--
  Reporter:  simon   | Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Changes (by simon):

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

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---