Edgewall Software

Changes between Version 4 and Version 5 of MarkupTemplates


Ignore:
Timestamp:
Jul 6, 2006, 8:46:35 PM (18 years ago)
Author:
cmlenz
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MarkupTemplates

    v4 v5  
    1313 * No generation of Python code for a template; the template is executed directly.
    1414 * No support for `<?python ?>` processing instructions
    15  * Expressions are evaluated in a more flexible manner, meaning you can use e.g. attribute access notation to access items in a dictionary, etc (see the [source:/trunk/markup/eval.py markup.eval] module)
     15 * Expressions are evaluated in a more flexible manner, meaning you can use e.g. dotten notation to access items in a dictionary, and the other way around (see the [source:/trunk/markup/eval.py markup.eval] module)
    1616 * Proper scoping of variables. Names do not leak into outer scopes.
    1717 * Use of XInclude and match templates instead of Kid's `py:extends` / `py:layout` directives