[issue5355] Expat parser error constants are string descriptions

Georg Brandl added the comment: You're completely correct, added one in r85528. Thanks! -- status: open -> closed ___ Python tracker ___ _

[issue5355] Expat parser error constants are string descriptions

Amaury Forgeot d'Arc added the comment: Please, add a tiny unit test for the presence of this feature. This is the only way for vm implementers to follow CPython development. -- nosy: +amaury.forgeotdarc stage: -> unit test needed status: closed -> open ___

[issue5355] Expat parser error constants are string descriptions

Georg Brandl added the comment: Fixed in r85526. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bug

[issue5355] Expat parser error constants are string descriptions

Georg Brandl added the comment: After talking to Fred, I'll add a "codes" attribute mapping the error constant strings to their codes. Changing the constants to integers would be very bad for b/w compatibility. -- assignee: -> georg.brandl nosy: +georg.brandl versions: +Python 3.2 -

[issue5355] Expat parser error constants are string descriptions

Suraj Barkale added the comment: In the snippet `ElementTree.parse('')` should be replaced by `ElementTree.fromstring('')`. ___ Python tracker ___

[issue5355] Expat parser error constants are string descriptions

New submission from Suraj Barkale : All the error constants in `xml.parsers.expat.errors` are strings. However, when expat raises an ExpatError exception, ExpatError.code attribute is a number. There seems to be no way of associating ExpatError with a corresponding error code from `xml.parsers.ex