> Also something that was brought up before but not really discussed, > Genshi. Do we want to continue trying to improve it or do we undertake > another template swap? This might even be too big a thing for 0.13, > but if 0.14 is to follow soon after we should probably work out an > official stance.
Currently, I am trying to improve on Genshi performance. I now have written a stream api that will eliminate current practice of processing a stream and collecting stream events into a single list over and over again. This, at least in my opinion is one of the major bottlenecks in overall Genshi performance. I am currently having a hard time figuring out how to incorporate the directives into the new processing model, which is based on chained iterators rather than chained calls to generators and list processing. While not having done any full integration yet, I am confident that will boost overall performance by a few percents. And, with the then more clear architecture and hopefully reduced recursiveness and thus complexity, Genshi will become more accessible to other developers, so that more people can begin optimizing it. As for the switch. Please either stick to Genshi or make it so that you will provide support for both Genshi and the new templating engine, so that when we are done with Genshi optimization, we do not have such hard times of going back to Genshi as an alternative. Regards -- Carsten -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to trac-...@googlegroups.com. To unsubscribe from this group, send email to trac-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
