[issue23019] pyexpat.errors wrongly bound to message strings instead of message codes
Björn Karge added the comment: I strongly disagree. The constants are just useless as they are (so this bug can hardly be considered a feature). The behaviour is not matching the 2.7 docs, so fixing it certainly won't be adding a new feature, and the python 3 behaviour can easily be preserved even if these constants are numbers. -- status: closed -> open ___ Python tracker <http://bugs.python.org/issue23019> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23019] pyexpat.errors wrongly bound to message strings instead of message codes
New submission from Björn Karge: expat.errors should expose the enum values and NOT the associated message strings, so they can be tested against ExpatError.code -- components: Library (Lib) messages: 232348 nosy: bkarge priority: normal severity: normal status: open title: pyexpat.errors wrongly bound to message strings instead of message codes type: behavior versions: Python 2.7 ___ Python tracker <http://bugs.python.org/issue23019> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
