Robin Bryce <robinbr...@gmail.com> added the comment: > 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. ---------- nosy: +robinbryce status: pending -> open _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue1538691> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
