I have started looking at what is missing for me to use this in my own projects, and the only big piece I could find missing for my purposes was XPathRegisterFunction. So I am starting to hack at it. (I know Python well, libxml2 somewhat though mostly as a user, and I am new to Pyrex. Great opportunity to learn, I love it so far.)
Ah, great, a contributor! :)
!!! I am sure those are always scarce. I cannot put tons of time either, but I am looking around at this point. First, I (finally) realized that the XPath support is in Python and not that of libxml. Oupse! I had misguided expectations to the contrary. I suggest you add this to the TODO. Your previous mails seem to indicate that this is a temporary situation. What are your plans exactly? And why did you start out this way? Did you look at interfacing with XPaths and see obvious problems that I do not know about? Otherwise, I would tend to say that the first thing to do is to declare a new XPathParserContext at xmlDoc creation, attach it to the xmlDoc instance, and use it for all later queries. Does that make sense to you? I am trying to look at the pitfalls, here. Marc-Antoine Parent
Hey, I seem to have missed this particular mail somehow, but there's an elmement in it that confuses me: Marc-Antoine Parent wrote: [snip]
First, I (finally) realized that the XPath support is in Python and not that of libxml. Oupse! I had misguided expectations to the contrary. I suggest you add this to the TODO.
Your previous mails seem to indicate that this is a temporary situation. What are your plans exactly? And why did you start out this way? Did you look at interfacing with XPaths and see obvious problems that I do not know about?
I'm confused about this -- the xpath support isn't using Python code, but is using libxml2's. The support for ElementTree style *find* is in Python, but xpath is using the underlying libxml2 engine. Regards, Martijn
participants (2)
-
Marc-Antoine Parent -
Martijn Faassen