![](https://secure.gravatar.com/avatar/1833d9a7642a05ddea0d27de72be2e2b.jpg?s=120&d=mm&r=g)
28 Nov
2006
28 Nov
'06
5:10 p.m.
Luke Tucker wrote:
It wouldn't be on the C side, but I think lxml might stick close enough to the ElementTree api to use their python xinclude implementation (ElementInclude.py) which does support the specification of a resolver if you need it. If you don't want to use that directly, it's probably a decent example. There is also a modified version of it that we use with lxml in Deliverance, but it's recursive I believe.
It is, right. For a Python-based solution in lxml, I'd personally prefer something based on getiterator("{http://.../xinclude}include"), should be much faster. Maybe we could even switch to something like that internally in lxml... Stefan