On 27 September 2010 17:16, Luke Plant <[email protected]> wrote: > Anyway, this seems good to me, and I can't think of a better place. For > the probably rare case of putting logging calls in your settings.py > (like Hanne Moa does), there is nothing to stop you setting up logging > yourself inside settings.py, which Hanne must presumably do already. > The only problem is that logging could be set up twice. For this case, > I guess we could support some convention like 'LOGGING_CONFIG = None' to > stop Django configuring logging altogether and add a note in the docs. > This might also be useful for the command line app situation.
This might be useful for switching over to the official logging system, easily turning it on and off. I've been using the logging system since before it was added to python. There used to be problems with it hiding some exceptions but that was in some hideously complex threads, multicast and ldap-disaster, so it might have been something else hiding those exceptions. I haven't seen any such in the duct tape-and-chewing gum setup I use in my django projects right now. If anyone is looking for inspiration: most modules longer than twenty lines starts with import logging _LOG = logging.getLogger(__name__) _LOG.info(__name__) .. so I know that they imported correctly on the production-server. I've also on occasion used decorators to log state on entry and exit of views and functions, in addition to liberal sprinkling through code that really ought to be refactored. I even add it to django itself in order to understand what's going on. HM -- 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.
