![](https://secure.gravatar.com/avatar/8b97b5aad24c30e4a1357b38cc39aeaa.jpg?s=120&d=mm&r=g)
7 Feb
2009
7 Feb
'09
9:17 p.m.
Christian Heimes wrote:
I guess it was a relict from the time lxml.etree didn't clear the local error log when an XSLT document was called.
I think you are referring to the error log on XSLT objects, which is actually local to the object and cleared before each transformation. (A copy of) the global error log is attached to exceptions, so you will notice the difference when you do multiple transformations and one of the later ones raises an exception. I guess there might still be space left for improvements... Stefan