re: verbose logging configuration.
This bothered me as well initially, though after starting to use
logging extensively I realized that there isn't really a more concise
way to provide all of the features that the logging config brings to
the table.
We can however, create a very concise default setup that mimics the
current admin-email behavior and provide additional documentation on
having more complex setups on djangoproject.com
ie:
LOGGING = {
'handlers': {
'mail_admins': { 'level': 'ERROR', 'class':
'django.utils.log.AdminEmailHandler' }
}
'loggers': {
'django': { 'handlers': ['mail_admins'], 'level':
'ERROR', 'propagate': True }
}
}
Regarding the 'version' setting.. .is that in the python 2.7
implementation? I ended up removing it from the included
logging-config in lumberjack as it wasn't really doing much.
I'm really pretty excited about this making it into 1.3... Thanks
guys! I haven't looked at the code extensively, but it looks really
good (a lot of improvements over what I had). I will take it for a
test drive this weekend though.
-k
On Thu, Sep 30, 2010 at 8:41 PM, Russell Keith-Magee
<russ...@keith-magee.com> wrote:
> On Fri, Oct 1, 2010 at 1:53 AM, Andy McCurdy <sed...@gmail.com> wrote:
>> Russ,
>> This will be a welcomed addition to debugging Django apps. I have a question
>> about startup.py. I notice that startup runs after settings are loaded, but
>> before models. Does this mean that code within startup.py cannot safely
>> access the ORM? If the ORM is fully accessible in startup.py, it's safe to
>> ignore the rest of the mail.
>
> The startup.py proposal has been dropped from the RC version of this patch.
>
> I still believe that there is a strong need for a 'startup logic'
> entry point, but it isn't required for the purposes of logging, and
> there is a significant overlap with the concerns of the AppCache
> refactor that was the subject of a SoC project this year. Rather than
> introduce an interface that wasn't strictly needed and was potentially
> going to be deprecated in the next release, we have opted to leave out
> this piece of functionality.
>
> 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 django-develop...@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.
>
>
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@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.
