Early on I was bit by a Kid bug (since fixed) not recognizing some &code;s, Maybe its the doco and maybe it's me, but I've had a lot of trouble getting Kid's behavior match what I read. Finally, trying to create unit test with webunit's DOM parser, I had some admittedly unreproducible problems getting parsable code with input that I'm pretty sure was valid (as I said, I couldn't go back and recreate the error, so I can't point to a specific problem).
Cheetah, OTOH, I've found much easier to ramp up with and does exactly what I expect it too. I'd been expecting to use it for non-XML templating anyway, so for me there's very little downside. Besides, Guido seemed to like Cheetah best, so it must be good;) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
