Right. I somehow missed that entire conversation!
Thanks guys - I'm going back to bed :-)
--Simon
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to dj
On 9/13/06, SmileyChris <[EMAIL PROTECTED]> wrote:
>
> This suggestion was dismissed pretty fast last time it brought up. I
> don't think this is the direction that the Django developers want to go
> down.
>
You can find that discussion here:
http://groups.google.com/group/django-developers/brow
This suggestion was dismissed pretty fast last time it brought up. I
don't think this is the direction that the Django developers want to go
down.
Have you checked out my AutoEscaping alternative?
(http://code.djangoproject.com/wiki/AutoEscape%20alternative#SuggestedSolution)
It's simple and effe
Hi guys,
I've been thinking about auto-escaping (due to another app I was having
issues with, and read the various auto-escaping proposals here on
Django-dev. I realise that this is largely solved by [1] and [2], but
just thought of another solution which might be easier than explicitly
turning
