Message74677
We had to be careful how we should handle this.
http://effbot.org/zone/element-iterparse.htm
A note on this site says following :
Note: The tree builder and the event generator are not necessarily
synchronized; the latter usually lags behind a bit. This means that when
you get a “start” event for an element, the builder may already have
filled that element with content. You cannot rely on this, though — a
“start” event can only be used to inspect the attributes, not the
element content. For more details, see this
<ref>http://mail.python.org/pipermail/xml-sig/2005-January/010838.html</ref>.
I do understand that it might be so that elem.text is undefined at start.
I have not investigated how iterparse handle this situation over boundaries:
<a> text <b> text </b> text </a> |
|
Date |
User |
Action |
Args |
2008-10-13 08:50:25 | roland | set | recipients:
+ roland, ocean-city |
2008-10-13 08:50:25 | roland | set | messageid: <1223887825.66.0.880282532683.issue4100@psf.upfronthosting.co.za> |
2008-10-13 08:50:24 | roland | link | issue4100 messages |
2008-10-13 08:50:23 | roland | create | |
|