+1 on the logging proposal. The stock python logging module is
definitely a bit of a finicky and confusing creature, especially for
people coming to Python for the first time with Django.
-0 On the signals based approach. I would be wary of the potential
performance overhead of replacing loggin
bad" thing here, they simply mirrored Django's own behavior.
As an interim solution I've forked django-html (http://github.com/
SeanOC/django-html) and added a middleware which does the XHTML=>HTML
string replacement. This is obviously a fairly messy approach but it
is the only
g
the code I wrote during the sprint and have posted a patch to the
related ticket (http://code.djangoproject.com/ticket/11863). You can
also get the code from http://github.com/SeanOC/django.
So far the patch is functional and has some basic unit tests but it is
not documented. I'll be work
> The first is that I'd like it to be compatible with deferred loading
> of model attributes - I haven't looked in to it, but my hunch is that
> this won't be too hard (it might even work in its present form without
> any further changes).
The current implementation doesn't support this. It wil
I've posted a new patch to the ticket (http://code.djangoproject.com/
ticket/11863) and have pushed my latest code to
http://github.com/SeanOC/django/tree/ticket11863. All of the issues
which Jacob raised should now be resolved and an initial version of
caching the query results has
