Issue 6265: cElementTree & ElementTree use different exceptions for XML Errors (original) (raw)

Issue6265

Created on 2009-06-11 10:46 by Neil Muller, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (2)
msg89247 - (view) Author: Neil Muller (Neil Muller) Date: 2009-06-11 10:46
cElementTree will raise a SyntaxError on XML parsing errors, while ElementTree will raise ExpatError. This makes changing between the two a bit more problematic than it could be. See for example https://lists.canonical.com/archives/bazaar/2006q3/017491.html ElementTree 1.3 raises a ParseError, which is subclassed from SyntaxError, which will improve the situation when it's merged, but cElementTree should be adjusted to raise the same error.
msg99406 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-02-16 13:13
Should be fixed with upstream ElementTree 1.3/cElementTree 1.0.6. See issue #6472.
History
Date User Action Args
2022-04-11 14:56:50 admin set github: 50514
2010-03-11 15:00:15 flox set status: open -> closedresolution: fixeddependencies: - Update ElementTree with upstream changessuperseder: Update ElementTree with upstream changesstage: resolved
2010-02-16 13:13:41 flox set priority: normalnosy: + floxmessages: + dependencies: + Update ElementTree with upstream changestype: behavior
2009-06-11 10:46:46 Neil Muller create