I would like to give a few more specifics about my "benchmarking". The web page had about 10 simple fields and a table of roughly 30 table rows. The method of generation the table rows was exactly the same as the example in the PyMeld documentation ie you create the Meld, you make a copy of a prototypr row instance, you generate your new rows, which may have replaceable fields inside them, and finally you replace the single prototype row with all the new rows you have generated. The same test using the same data with Cheetah and native templates resulted in (on an oldish 600Mhz box): PyMeld: +-300ms Cheetah: +-30ms Native %s: +- 5ms On newer hardware obviously the times will be very different but this particular application has to be able to scale to very large tables. I did not try PyMeldLite because the HTML I am using is exactlty that: HTML and not XHTML. Again I am not criticising PyMeld, I love its simplicity and clean api and the code is easily understandable so I will probably take a look at it again at some time. Also its great that it works with any snippet of HTML code it does not even have to be valid HTML and I get a lot of invalid HTML from the designers. Regarding Cheetah, I was using Cheetah 1.0. There is a 2.0 Release Candidate out but I didnt want to be using anything in RC status for a production site.
-- http://mail.python.org/mailman/listinfo/python-list
