Jinja Changelog¶

Version 2.10¶

released on November 8th 2017

  • Added a new extension node called OverlayScope which can be used tocreate an unoptimized scope that will look up all variables from aderived context.
  • Added an in test that works like the in operator. This can be usedin combination with reject and select.
  • Added previtem and nextitem to loop contexts, providing access to theprevious/next item in the loop. If such an item does not exist, the value isundefined.
  • Added changed(*values) to loop contexts, providing an easy way ofchecking whether a value has changed since the last iteration (or rathersince the last call of the method)
  • Added a namespace function that creates a special object which allowsattribute assignment using the set tag. This can be used to carry dataacross scopes, e.g. from a loop body to code that comes after the loop.
  • Added a trimmed modifier to {% trans %} to strip linebreaks andsurrounding whitespace. Also added a new policy to enable this for alltrans blocks.
  • The random filter is no longer incorrectly constant folded and willproduce a new random choice each time the template is rendered. (#478)
  • Added a unique filter. (#469)
  • Added min and max filters. (#475)
  • Added tests for all comparison operators: eq, ne, lt, le,gt, ge. (#665)
  • import statement cannot end with a trailing comma. (#617, #618)
  • indent filter will not indent blank lines by default. (#685)
  • Add reverse argument for dictsort filter. (#692)
  • Add a NativeEnvironment that renders templates to native Python typesinstead of strings. (#708)
  • Added filter support to the block set tag. (#489)
  • tojson filter marks output as safe to match documented behavior.(#718)
  • Resolved a bug where getting debug locals for tracebacks couldmodify template context.
  • Fixed a bug where having many {% elif … %} blocks resulted in a“too many levels of indentation” error. These blocks now compile tonative elif ..: instead of else: if ..: (#759)

Version 2.9.6¶

(bugfix release, released on April 3rd 2017)

  • Fixed custom context behavior in fast resolve mode (#675)

Version 2.9.5¶

(bugfix release, released on January 28th 2017)

  • Restored the original repr of the internal _GroupTuple because thiscaused issues with ansible and it was an unintended change. (#654)
  • Added back support for custom contexts that override the old resolvemethod since it was hard for people to spot that this could cause aregression.
  • Correctly use the buffer for the else block of for loops. This causedinvalid syntax errors to be caused on 2.x and completely wrong behavioron Python 3 (#669)
  • Resolve an issue where the {% extends %} tag could not be used withasync environments. (#668)
  • Reduce memory footprint slightly by reducing our unicode database dumpwe use for identifier matching on Python 3 (#666)
  • Fixed autoescaping not working for macros in async compilation mode. (#671)

Version 2.9.4¶

(bugfix release, released on January 10th 2017)

  • Solved some warnings for string literals. (#646)
  • Increment the bytecode cache version which was not done due to anoversight before.
  • Corrected bad code generation and scoping for filtered loops. (#649)
  • Resolved an issue where top-level output silencing after known extendblocks could generate invalid code when blocks where contained in ifstatements. (#651)
  • Made the truncate.leeway default configurable to improve compatibilitywith older templates.

Version 2.9.3¶

(bugfix release, released on January 8th 2017)

  • Restored the use of blocks in macros to the extend that was possiblebefore. On Python 3 it would render a generator repr instead ofthe block contents. (#645)
  • Set a consistent behavior for assigning of variables in inner scopeswhen the variable is also read from an outer scope. This now sets theintended behavior in all situations however it does not restore theold behavior where limited assignments to outer scopes was possible.For more information and a discussion see #641
  • Resolved an issue where block scoped would not take advantage of thenew scoping rules. In some more exotic cases a variable overriden in alocal scope would not make it into a block.
  • Change the code generation of the with statement to be in line with thenew scoping rules. This resolves some unlikely bugs in edge cases. Thisalso introduces a new internal With node that can be used by extensions.

Version 2.9.2¶

(bugfix release, released on January 8th 2017)

  • Fixed a regression that caused for loops to not be able to use the samevariable for the target as well as source iterator. (#640)
  • Add support for a previously unknown behavior of macros. It used to bepossible in some circumstances to explicitly provide a caller argumentto macros. While badly buggy and unintended it turns out that this is acommon case that gets copy pasted around. To not completely break backwardscompatibility with the most common cases it’s now possible to provide anexplicit keyword argument for caller if it’s given an explicit default.(#642)

Version 2.9.1¶

(bugfix release, released on January 7th 2017)

  • Resolved a regression with call block scoping for macros. Nested callerblocks that used the same identifiers as outer macros could refer to thewrong variable incorrectly.

Version 2.9¶

(codename Derivation, released on January 7th 2017)

  • Change cache key definition in environment. This fixes a performanceregression introduced in 2.8.
  • Added support for generator_stop on supported Python versions(Python 3.5 and later)
  • Corrected a long standing issue with operator precedence of math operationsnot being what was expected.
  • Added support for Python 3.6 async iterators through a new async mode.
  • Added policies for filter defaults and similar things.
  • urlize now sets “rel noopener” by default.
  • Support attribute fallback for old-style classes in 2.x.
  • Support toplevel set statements in extend situations.
  • Restored behavior of Cycler for Python 3 users.
  • Subtraction now follows the same behavior as other operators on undefinedvalues.
  • map and friends will now give better error messages if you forgot toquote the parameter.
  • Depend on MarkupSafe 0.23 or higher.
  • Improved the truncate filter to support better truncation in casethe string is barely truncated at all.
  • Change the logic for macro autoescaping to be based on the runtimeautoescaping information at call time instead of macro define time.
  • Ported a modified version of the tojson filter from Flask to Jinja2and hooked it up with the new policy framework.
  • Block sets are now marked safe by default.
  • On Python 2 the asciification of ASCII strings can now be disabled withthe compiler.ascii_str policy.
  • Tests now no longer accept an arbitrary expression as first argument buta restricted one. This means that you can now properly use multipletests in one expression without extra parentheses. In particular you cannow write foo is divisibleby 2 or foo is divisibleby 3as you would expect.
  • Greatly changed the scoping system to be more consistent with what templatedesigners and developers expect. There is now no more magic differencebetween the different include and import constructs. Context is now alwayspropagated the same way. The only remaining differences is the defaultsfor with context and without context.
  • The with and autoescape tags are now built-in.
  • Added the new select_autoescape function which helps configuring betterautoescaping easier.
  • Fixed a runtime error in the sandbox when attributes of async generatorswere accessed.

Version 2.8.1¶

(bugfix release, released on December 29th 2016)

  • Fixed the for_qs flag for urlencode.
  • Fixed regression when applying int to non-string values.
  • SECURITY: if the sandbox mode is used format expressions are now sandboxedwith the same rules as in Jinja. This solves various information leakageproblems that can occur with format strings.

Version 2.8¶

(codename Replacement, released on July 26th 2015)

  • Added target parameter to urlize function.
  • Added support for followsymlinks to the file system loader.
  • The truncate filter now counts the length.
  • Added equalto filter that helps with select filters.
  • Changed cache keys to use absolute file names if availableinstead of load names.
  • Fixed loop length calculation for some iterators.
  • Changed how Jinja2 enforces strings to be native strings inPython 2 to work when people break their default encoding.
  • Added make_logging_undefined() which returns an undefinedobject that logs failures into a logger.
  • If unmarshalling of cached data fails the template will bereloaded now.
  • Implemented a block set tag.
  • Default cache size was increased to 400 from a low 50.
  • Fixed is number test to accept long integers in all Python versions.
  • Changed is number to accept Decimal as a number.
  • Added a check for default arguments followed by non-default arguments. Thischange makes {% macro m(x, y=1, z) %}…{% endmacro %} a syntax error.The previous behavior for this code was broken anyway (resulting in thedefault value being applied to y).
  • Add ability to use custom subclasses of jinja2.compiler.CodeGenerator andjinja2.runtime.Context by adding two new attributes to the environment(code_generator_class and context_class) (pull request #404).
  • added support for context/environment/evalctx decorator functions onthe finalize callback of the environment.
  • escape query strings for urlencode properly. Previously slashes were notescaped in that place.
  • Add ‘base’ parameter to ‘int’ filter.

Version 2.7.3¶

(bugfix release, released on June 6th 2014)

  • Security issue: Corrected the security fix for the cache folder. Thisfix was provided by RedHat.

Version 2.7.2¶

(bugfix release, released on January 10th 2014)

  • Prefix loader was not forwarding the locals properly toinner loaders. This is now fixed.
  • Security issue: Changed the default folder for the filesystem cache to beuser specific and read and write protected on UNIX systems. SeeDebian bug 734747 for more information.

Version 2.7.1¶

(bugfix release, released on August 7th 2013)

  • Fixed a bug with call_filter not working properly on environmentand context filters.
  • Fixed lack of Python 3 support for bytecode caches.
  • Reverted support for defining blocks in included templates as thisbroke existing templates for users.
  • Fixed some warnings with hashing of undefineds and nodes if Pythonis run with warnings for Python 3.
  • Added support for properly hashing undefined objects.
  • Fixed a bug with the title filter not working on already uppercasestrings.

Version 2.7¶

(codename Translation, released on May 20th 2013)

  • Choice and prefix loaders now dispatch source and template lookupseparately in order to work in combination with module loaders asadvertised.
  • Fixed filesizeformat.
  • Added a non-silent option for babel extraction.
  • Added urlencode filter that automatically quotes values forURL safe usage with utf-8 as only supported encoding. If applicationswant to change this encoding they can override the filter.
  • Added keep-trailing-newline configuration to environments andtemplates to optionally preserve the final trailing newline.
  • Accessing last on the loop context no longer causes the iteratorto be consumed into a list.
  • Python requirement changed: 2.6, 2.7 or >= 3.3 are required now,supported by same source code, using the “six” compatibility library.
  • Allow contextfunction and other decorators to be applied to call.
  • Added support for changing from newline to different signs in the wordwrapfilter.
  • Added support for ignoring memcache errors silently.
  • Added support for keeping the trailing newline in templates.
  • Added finer grained support for stripping whitespace on the left sideof blocks.
  • Added map, select, reject, selectattr and rejectattrfilters.
  • Added support for loop.depth to figure out how deep inside a recursiveloop the code is.
  • Disabled py_compile for pypy and python 3.

Version 2.6¶

(codename Convolution, released on July 24th 2011)

  • internal attributes now raise an internal attribute error now insteadof returning an undefined. This fixes problems when passing undefinedobjects to Python semantics expecting APIs.
  • traceback support now works properly for PyPy. (Tested with 1.4)
  • implemented operator intercepting for sandboxed environments. Thisallows application developers to disable builtin operators for bettersecurity. (For instance limit the mathematical operators to actualintegers instead of longs)
  • groupby filter now supports dotted notation for grouping by attributesof attributes.
  • scoped blocks now properly treat toplevel assignments and imports.Previously an import suddenly “disappeared” in a scoped block.
  • automatically detect newer Python interpreter versions before loading codefrom bytecode caches to prevent segfaults on invalid opcodes. The segfaultin earlier Jinja2 versions here was not a Jinja2 bug but a limitation inthe underlying Python interpreter. If you notice Jinja2 segfaulting inearlier versions after an upgrade of the Python interpreter you don’t haveto upgrade, it’s enough to flush the bytecode cache. This just no longermakes this necessary, Jinja2 will automatically detect these cases now.
  • the sum filter can now sum up values by attribute. This is a backwardsincompatible change. The argument to the filter previously was theoptional starting index which defaults to zero. This now became thesecond argument to the function because it’s rarely used.
  • like sum, sort now also makes it possible to order items by attribute.
  • like sum and sort, join now also is able to join attributes of objectsas string.
  • the internal eval context now has a reference to the environment.
  • added a mapping test to see if an object is a dict or an object witha similar interface.

Version 2.5.5¶

(re-release of 2.5.4 with built documentation removed for filesize.
Released on October 18th 2010)

  • built documentation is no longer part of release.

Version 2.5.4¶

(bugfix release, released on October 17th 2010)

  • Fixed extensions not loading properly with overlays.
  • Work around a bug in cpython for the debugger that causes segfaultson 64bit big-endian architectures.

Version 2.5.3¶

(bugfix release, released on October 17th 2010)

  • fixed an operator precedence error introduced in 2.5.2. Statementslike “-foo.bar” had their implicit parentheses applied around thefirst part of the expression (“(-foo).bar”) instead of the morecorrect “-(foo.bar)”.

Version 2.5.2¶

(bugfix release, released on August 18th 2010)

  • improved setup.py script to better work with assumptions peoplemight still have from it (—with-speedups).
  • fixed a packaging error that excluded the new debug support.

Version 2.5.1¶

(bugfix release, released on August 17th 2010)

  • StopIteration exceptions raised by functions called from templatesare now intercepted and converted to undefineds. This solves alot of debugging grief. (StopIteration is used internally toabort template execution)
  • improved performance of macro calls slightly.
  • babel extraction can now properly extract newstyle gettext calls.
  • using the variable num in newstyle gettext for something elsethan the pluralize count will no longer raise a KeyError.
  • removed builtin markup class and switched to markupsafe. For backwardscompatibility the pure Python implementation still exists but ispulled from markupsafe by the Jinja2 developers. The debug supportwent into a separate feature called “debugsupport” and is disabledby default because it is only relevant for Python 2.4
  • fixed an issue with unary operators having the wrong precedence.

Version 2.5¶

(codename Incoherence, released on May 29th 2010)

  • improved the sort filter (should have worked like this for along time) by adding support for case insensitive searches.
  • fixed a bug for getattribute constant folding.
  • support for newstyle gettext translations which result in anicer in-template user interface and more consistentcatalogs. (Whitespace Trimming)
  • it’s now possible to register extensions after an environmentwas created.

Version 2.4.1¶

(bugfix release, released on April 20th 2010)

  • fixed an error reporting bug for undefineds.

Version 2.4¶

(codename Correlation, released on April 13th 2010)

  • the environment template loading functions now transparentlypass through a template object if it was passed to it. Thismakes it possible to import or extend from a template objectthat was passed to the template.
  • added a ModuleLoader that can load templates fromprecompiled sources. The environment now features a methodto compile the templates from a configured loader into a zipfile or folder.
  • the _speedups C extension now supports Python 3.
  • added support for autoescaping toggling sections and supportfor evaluation contexts (Evaluation Context).
  • extensions have a priority now.

Version 2.3.1¶

(bugfix release, released on February 19th 2010)

  • fixed an error reporting bug on all python versions
  • fixed an error reporting bug on Python 2.4

Version 2.3¶

(codename 3000 Pythons, released on February 10th 2010)

  • fixes issue with code generator that causes unbound variablesto be generated if set was used in if-blocks and other smallidentifier problems.
  • include tags are now able to select between multiple templatesand take the first that exists, if a list of templates isgiven.
  • fixed a problem with having call blocks in outer scopes thathave an argument that is also used as local variable in aninner frame (#360).
  • greatly improved error message reporting (#339)
  • implicit tuple expressions can no longer be totally empty.This change makes {% if %}…{% endif %} a syntax errornow. (#364)
  • added support for translator comments if extracted via babel.
  • added with-statement extension.
  • experimental Python 3 support.

Version 2.2.1¶

(bugfix release, released on September 14th 2009)

  • fixes some smaller problems for Jinja2 on Jython.

Version 2.2¶

(codename Kong, released on September 13th 2009)

  • Include statements can now be marked with ignore missing to skipnon existing templates.
  • Priority of not raised. It’s now possible to write not foo in bar_as an alias to _foo not in bar like in python. Previously the grammarrequired parentheses (not (foo in bar)) which was odd.
  • Fixed a bug that caused syntax errors when defining macros or using the{% call %} tag inside loops.
  • Fixed a bug in the parser that made {{ foo[1, 2] }} impossible.
  • Made it possible to refer to names from outer scopes in included templatesthat were unused in the callers frame (#327)
  • Fixed a bug that caused internal errors if names where used as iterationvariable and regular variable after the loop if that variable was unusedbefore the loop. (#331)
  • Added support for optional scoped modifier to blocks.
  • Added support for line-comments.
  • Added the meta module.
  • Renamed (undocumented) attribute “overlay” to “overlayed” on theenvironment because it was clashing with a method of the same name.
  • speedup extension is now disabled by default.

Version 2.1.1¶

(bugfix release, released on December 25th 2008)

  • Fixed a translation error caused by looping over empty recursive loops.

Version 2.1¶

(codename Yasuzō, released on November 23rd 2008)

  • fixed a bug with nested loops and the special loop variable. Before thechange an inner loop overwrote the loop variable from the outer one afteriteration.
  • fixed a bug with the i18n extension that caused the explicit pluralizationblock to look up the wrong variable.
  • fixed a limitation in the lexer that made {{ foo.0.0 }} impossible.
  • index based subscribing of variables with a constant value returns anundefined object now instead of raising an index error. This was a bugcaused by eager optimizing.
  • the i18n extension looks up foo.ugettext now followed by foo.gettextif an translations object is installed. This makes dealing with customtranslations classes easier.
  • fixed a confusing behavior with conditional extending. loops were partiallyexecuted under some conditions even though they were not part of a visiblearea.
  • added sort filter that works like dictsort but for arbitrary sequences.
  • fixed a bug with empty statements in macros.
  • implemented a bytecode cache system. (Bytecode Cache)
  • the template context is now weakref-able
  • inclusions and imports “with context” forward all variables now, not onlythe initial context.
  • added a cycle helper called cycler.
  • added a joining helper called joiner.
  • added a compile_expression method to the environment that allows compilingof Jinja expressions into callable Python objects.
  • fixed an escaping bug in urlize

Version 2.0¶

(codename jinjavitus, released on July 17th 2008)

  • the subscribing of objects (looking up attributes and items) changed fromslightly. It’s now possible to give attributes or items a higher priorityby either using dot-notation lookup or the bracket syntax. This alsochanged the AST slightly. Subscript is gone and was replaced withGetitem and Getattr.

For more information see the implementation details.

  • added support for preprocessing and token stream filtering for extensions.This would allow extensions to allow simplified gettext calls in templatedata and something similar.

  • added jinja2.environment.TemplateStream.dump().

  • added missing support for implicit string literal concatenation.{{ "foo" "bar" }} is equivalent to {{ "foobar" }}

  • else is optional for conditional expressions. If not given it evaluatesto false.

  • improved error reporting for undefined values by providing a position.

  • filesizeformat filter uses decimal prefixes now per default and can beset to binary mode with the second parameter.

  • fixed bug in finalizer

Version 2.0rc1¶

(no codename, released on June 9th 2008)

  • first release of Jinja2

原文:

http://jinja.pocoo.org/docs/2.10/changelog/