-
-
Notifications
You must be signed in to change notification settings - Fork 16.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
turn on autoescape for flask.templating.render_template_string
#1176
Conversation
Sensible or not, this is a drastical change in behavior and a breakage of the API that deserves more discussion than just a simple PR. |
@untitaker sure, where do we start? |
There are a few questions unanswered:
|
This search finds too many usages than I know how to deal with, so just a note in the release changes?
I'm always for breaking compatibility in favor of better defaults, but it's not only my decision.
@mitsuhiko any input? |
What should we do about this? If this pull request isn't going to be merged I'll remove it... |
I think it should be included in 1.0, but mitsuhiko should decide. It doesn't seem that he is reachable atm, but please reopen anyway. On 23 June 2015 09:34:05 CEST, Alan Hamlett [email protected] wrote:
|
I deleted the fork, so can't reopen. Created a new pull request #1515. |
This seems like a sane default, since Flask turns on autoescape by default for html files when using the more common
render_template
so users will be expectingrender_template_string
to autoescape their template variables.