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:

• How to deal with code that relies on the current default
• Whether the change is worth the compatibility breakage
• Which reasons @mitsuhiko originally had for the current default

How to deal with code that relies on the current default

This search finds too many usages than I know how to deal with, so just a note in the release changes?
https://github.com/search?q=render_template_string&type=Code

Whether the change is worth the compatibility breakage

I'm always for breaking compatibility in favor of better defaults, but it's not only my decision.

Which reasons @mitsuhiko originally had for the current default

@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 notifications@github.com wrote:

Closed #1176.

---

Reply to this email directly or view it on GitHub:
#1176 (comment)

I deleted the fork, so can't reopen. Created a new pull request #1515.