On Oct 4, 9:22 pm, Ivan Sagalaev <man...@softwaremaniacs.org> wrote:
> I see one problem with explicitly calling a function from settings.py.
> This will execute instantiation of handlers and all the user staff very
> early when settings aren't fully configured yet. This prevents a user to
> have a handler that will use Django models for example. In general
> settings should be as dumb as possible for easy bootstrapping. This is
> why all those middleware/context processors/backends etc are strings and
> not actual callables.
I can't say I'm too fond of behind-the-scenes magic and that's why I'd
prefer an explicit call to configure logging; otherwise users might
run into limitations such as the fact that you already can't import
certain things in settings.py without running into circular import
errors. I don't know how common a use case it might be to use Django
models in logging handlers.
Regards,
Vinay
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
