On Wed, Oct 6, 2010 at 6:53 AM, Russell Keith-Magee <[email protected] > wrote:
> That approach works (as in - it doesn't raise errors), but it means > that under Python 2.4, you lose any of the "extra" data. In > particular, it means that > * it's really hard to do anything interesting with the 4XX series errors, > * the HTTP 500 error emails won't have any details about the request > that caused them > * the DB logging calls won't include any details about the SQL that > was being logged. > The first and last don't bother me particularly -- they are new features that come with Django's use of logging and if they are not available under 2.4 I think that would be OK. That middle one is a killer though. What about just not adding the logging feature for Python 2.4? Make the calls conditional on Python version and fall back to old behavior in the 2.4 case? Not an approach we've taken before (that I can recall), but if the 2.4 level just doesn't do what we need it seems like it might be a reasonable restriction. Karen -- 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.
