Issue1850

classification
Title: ExpatError
Type: behaviour Severity: normal
Components: Versions: 2.5.2
process
Status: closed Resolution: invalid
Dependencies: Superseder:
Assigned To: Nosy List: pjenvey, ssteiner
Priority: Keywords:

Created on 2012-03-15.11:42:54 by ssteiner, last changed 2012-03-16.02:40:18 by pjenvey.

Messages
msg6796 (view) Author: simon steiner (ssteiner) Date: 2012-03-15.11:42:54
from xml.etree import ElementTree as et
et.ElementTree(et.XML('hi'))

cpython:
xml.parsers.expat.ExpatError: syntax error: line 1, column 0

jython:
xml.parsers.expat.ExpatError: Content is not allowed in prolog.
msg6800 (view) Author: Philip Jenvey (pjenvey) Date: 2012-03-16.02:40:17
I don't consider this a bug simply because the error message is different. Those are usually implementation details and they frequently change between versions so they shouldn't be relied upon

The ExpatError exception has lineno, offset and code variables if you need that information
History
Date User Action Args
2012-03-16 02:40:18pjenveysetstatus: open -> closed
resolution: invalid
messages: + msg6800
nosy: + pjenvey
2012-03-15 11:42:54ssteinercreate