Message194738
| Author | pitrou |
|---|---|
| Recipients | eli.bendersky, flox, jcea, pitrou, python-dev, scoder |
| Date | 2013-08-09.14:47:05 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <282093699.52926475.1376059619980.JavaMail.root@zimbra10-e2.priv.proxad.net> |
| In-reply-to | <1376058754.42.0.478779296961.issue17741@psf.upfronthosting.co.za> |
| Content | |
|---|---|
> But IncrementalParser uses an XMLParser internally, which in turn > uses a TreeBuilder internally. So what exactly is your point? Well, I would rather like to understand yours. Whatever IncrementalParser uses internally needn't impact what API it exposes to the user. (as a matter of fact, iterparse() doesn't expose a TreeBuilder-like API, either) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013-08-09 14:47:06 | pitrou | set | recipients: + pitrou, jcea, scoder, eli.bendersky, flox, python-dev |
| 2013-08-09 14:47:06 | pitrou | link | issue17741 messages |
| 2013-08-09 14:47:05 | pitrou | create | |