Steve Holden wrote: > Christoph Zwerschke wrote: >> First, in many cases, Kid should supplement the usual traceback with an >> output of the data or Python expression it was processing when the error >> occurred. This was already implemented for py:attrs expressions, for >> instance. Maybe I can do something similar for the XML() feature. Can >> you send me a small example template where you get such a meaningless >> message with XML()? I'll try to improve this and get it in Kid 0.9.4 >> which I think should appear soon. >> > Unfortunately it wouldn't be that easy, as the code is, as I mentioned, > an existing application with bits of the content generated all over the > place. I'd be happy to send you the whole thing, but it's currently a mess. > > Your awareness of the problem is sufficient - I'm currently back using > the original HTML generation methods for the moment.
Ok, I have improved this in the Kid trunk. If there is something wrong with the XML, the erroneous line of XML and the exact position of the error is now displayed. The error messages and behavior of py:extends and py:layout is now more intelligent, too. -- Christoph --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
