Fix issue #453 jinja2 template select_autoescape when using jinja2.select_autoescape #454
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I added a test to reproduce what was reported in #453 . Running the test first, without the patch, gives:
Hopefully Travis CI will report that this patch produced no failures in the tests. I avoided trying to check if the
jinja2
module was aliased, as I think we would have to look at the Context imports, store in a variable what was the method, and add yet anotherif
for that? But if there's a simpler way or if necessary, happy to update this pull request.Cheers
Bruno