On Sep 29, 2:35 pm, Ivan Sagalaev <man...@softwaremaniacs.org> wrote:
> Forgot one thing. As it stands now Django has this "historic" behavior
> when it imports and executes settings module twice. This results in
> breakage when you setup loggers and handlers by hand. We now circumvent
> this by having a helper function that memoizes configured loggers and
> call it from settings.py. Having a declarative config we can hide this
> inside of Django and not scare users.
This is how the way basicConfig works actually helps - it's a no-op if
you call it again. (It wasn't done that way for use with Django
particularly - just to make life easier for newbies and casual users.
Sure, an internal function would hide this from users.
Regards,
Vinay Sajip
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
