The compilation strategy has been changed in the most recent Chameleon
release (1.0b11).

Instead of using Python's built-in ``pycodegen`` module to generate
byte-code from the AST, we're now using a new invention of mine,
``sourcecodegen``, to actually create Python source-code from the AST
in order to use the built-in source-code compiler. This may seem
backwards, but it has several advantages:

1) Debugging is easier, because what you see is what you get.
2) No magic insertion of globals; the source-code is by necessity self-contained
3) There's no longer an artificial template size limit (as previously
imposed due to stack size reasons)

I've issued new releases of all involved packages.

I've also corrected a benchmark comparing performance between
preparing Chameleon and ZPT for rendering (e.g. parsing/compilation
steps). Chameleon is still quite slow on a cold boot (30 times
slower), but when the cache is used (e.g. "warm boot"), there's only a
factor of 1.25 to differ.


You received this message because you are subscribed to the Google Groups 
"" group.
To post to this group, send email to
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at

Reply via email to