Message86120
> In the upstream 1.0.6, the ParseError exception has a position attribute
> that contains a (line, column) tuple.
That's fine for errors in the xml domain. Its not enough if I'm
reporting errors in the application domain - where I wont have a handy
exception to interrogate. What's the problem with just exposing the api
and requiring users who need it to use the streaming parser ?
Personally, I would have cached these details as a properties of the
_ElementInterface implementation for precisely this use case. |
|
Date |
User |
Action |
Args |
2009-04-18 15:10:58 | robinbryce | set | recipients:
+ robinbryce, effbot, nnorwitz, georg.brandl, robinbryce2 |
2009-04-18 15:10:56 | robinbryce | set | messageid: <1240067456.91.0.477273338385.issue1538691@psf.upfronthosting.co.za> |
2009-04-18 15:10:55 | robinbryce | link | issue1538691 messages |
2009-04-18 15:10:55 | robinbryce | create | |
|