This seems odd, because autoescaping has been on since almost the beginning.
https://web.archive.org/web/20080826081214/http://docs.djangoproject.com:80/en/dev/topics/templates/#id2
What actually changed with 1.9?
> On Feb 13, 2018, at 7:53 AM, Bill Torcaso wrote:
>
>
autoescape has defaulted to on since before Django 1.0; it was a massive change
at the time.
The only change in escaping behaviour in 1.9 was around the output of simple
tags, see
https://docs.djangoproject.com/en/2.0/releases/1.9/#simple-tag-now-wraps-tag-output-in-conditional-escape
- this
o: Django users
Subject: Migrating into Django 1.9; question about autoescape
Hello all,
I have the task of migrating a very old website from Django 1.7 to either
Django 1.11 or 2.0, depending on the effort.
My plan is to go from 1.7 --> 1.8 --> 1.9 -->1.10 --> 1.11, adapting the
co
Hello all,
I have the task of migrating a very old website from Django 1.7 to either
Django 1.11 or 2.0, depending on the effort.
My plan is to go from 1.7 --> 1.8 --> 1.9 -->1.10 --> 1.11, adapting the
codebase as I go. It's been easy enough until I arrive at 1.9, and the
change in
4 matches
Mail list logo