On Wed, Oct 6, 2010 at 8:08 PM, Luke Plant <[email protected]> wrote: > On Wed, 2010-10-06 at 12:24 +0800, Russell Keith-Magee wrote: > >> A fourth option would be to include Python's logging module, much as >> we do with doctest, simpleJSON, and we're about to do with unittest2. >> It's a heavyweight option, but it would do the job. We could remove >> the inclusion once we drop Python 2.4 support (possibly in Django >> 1.4). > > Would this actually work? If any other library in someone's application > uses 'import logging', they will get the system logging module, and > unlike with those other libraries, this matters because logging has its > own global objects and configuration etc. If we had our own in > django.utils.logging, we would end up with two logging systems being > used, which is going to get very ugly very quickly.
Yeah... on second thoughts, this approach probably wouldn't work due to the global/singleton issues. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
