| Weblog: | The Python comunity has too many deceptive XML benchmarks | |
| Subject: | Trying my own tool (Gnosis Utils) | |
| Date: | 2005-01-24 20:03:21 | |
| From: | David_Mertz | |
|
Response to: Trying my own tool (Gnosis Utils)
|
||
|
I am thinking, BTW, of wrapping cElementTree.iterparse() into another gnosis.xml.objectify parser. Currently, there's a painfully slow DOM parser, and a reasonably fast EXPAT parser in there. But the design makes it easy to plug in something else. I have vaguely wanted to create an RXPU parser too (and more recently LXML)... but if I think cElementTree is even faster, I might just do that.
|
||
Showing messages 1 through 2 of 2.
-
Trying my own tool (Gnosis Utils)
2005-01-25 15:08:00 effbot [Reply | View]
-
Trying my own tool (Gnosis Utils)
2005-01-26 00:16:11 David_Mertz [Reply | View]
Fredrik is, of course, just simply wrong about namespaces in gnosis.xml.objectify. But I admit that I haven't documented the "enable namespaces" switch as well as I should have. I inherit the issue from the pyexpat code, but I should make the stuff work a bit more easily.
Then again, from what I can infer (from some private email), Fredrik also seems to believe that gnosis.xml.objectify only uses the original DOM parser, rather than also (and now by default) using the EXPAT style that it's had since before the first version of ElementTree was created.
Unfortunately, /F's demeanor and tact has taken a big turn for the worse.
| Showing messages 1 through 2 of 2. |




and of course you should take advantage of the stuff I'm doing. it may not save you that much, since you still have to create all the objects over at the python side of things, but it's worth trying. drop me a line if you have questions.