From: Tim Gates Date: Wed, 4 Sep 2019 22:12:07 +0000 (+1000) Subject: Fix simple typo: problemtic -> problematic (#1059) X-Git-Tag: 2.11.0~65 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=91a404073acac40a7945bf7d584e8b30bc7a08cb;p=thirdparty%2Fjinja.git Fix simple typo: problemtic -> problematic (#1059) Plus rephrase the comment for greater clarity. --- diff --git a/jinja2/runtime.py b/jinja2/runtime.py index 92cd99a6..b37465a9 100644 --- a/jinja2/runtime.py +++ b/jinja2/runtime.py @@ -500,9 +500,8 @@ class Macro(object): # decide largely based on compile-time information if a macro is # safe or unsafe. While there was a volatile mode it was largely # unused for deciding on escaping. This turns out to be - # problemtic for macros because if a macro is safe or not not so - # much depends on the escape mode when it was defined but when it - # was used. + # problematic for macros because whether a macro is safe depends not + # on the escape mode when it was defined, but rather when it was used. # # Because however we export macros from the module system and # there are historic callers that do not pass an eval context (and