Fredrik Lundh wrote:
> by using it to split your document into reasonably-sized chunks (one
> record, one expression, one text block, one paragraph, etc), and using
> Python code to process the chunks.
I've updated cElementTree/iterparse implementation to build one full
expression at a time.
htt
K.S.Sreeram wrote:
> From what i understand, the iterparse interface constructs the xml tree,
> but gives you hooks into the tree construction process itself, so that
> the programmer can control how much state he wants to retain and how
> much state he can discard.
>
> I wanted the test program
Fredrik Lundh wrote:
> your celementtree example isn't exactly optimal, though... are you sure
> you understand how iterparse works?
From what i understand, the iterparse interface constructs the xml tree,
but gives you hooks into the tree construction process itself, so that
the programmer can
K.S.Sreeram wrote:
> All the recent discussions on xml parsing performance got me curious,
> and i put together a small speed test for xml processing.
your celementtree example isn't exactly optimal, though... are you sure
you understand how iterparse works?
--
http://mail.python.org/mailma
All the recent discussions on xml parsing performance got me curious,
and i put together a small speed test for xml processing.
The test program was designed to have as minimal state requirements as
possible so that efficient 'stream' processing can be done using sax
style events.
Here's the quic
