[issue23019] pyexpat.errors wrongly bound to message strings instead of message codes

[Serhiy Storchaka]

Serhiy Storchaka  added the comment:

Python 2.7 is no longer supported.

--
nosy: +serhiy.storchaka
resolution: wont fix -> out of date
stage: needs patch -> resolved
status: open -> closed

___
Python tracker 

___
___
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

[Tahia K]

Tahia K  added the comment:

Hi guys,

Is this issue still free to pick up?

--
nosy: +ta1hia

___
Python tracker 

___
___
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

[Martin Panter]

Martin Panter added the comment:

Also, even in the Py 3 docs, the ErrorCode parser attribute is said to be 
numeric, but there is a suggestion to compare it with “constants” defined in 
the “errors” (module) object. I guess it should be clarified that you can’t 
compare it directly; perhaps using ErrorString or Py 3’s “errors.codes” is more 
appropriate?

--
nosy: +martin.panter

___
Python tracker 

___
___
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

[R. David Murray]

R. David Murray added the comment:

For backward compatibility reasons this *can not be changed*.  We are stuck 
with it, even though we agree it is broken.  Please do not reopen the issue.

--
status: open - closed

___
Python tracker rep...@bugs.python.org
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

[R. David Murray]

R. David Murray added the comment:

Actually, I'm going to reopen it as a doc issue. This should be explained in 
the 2.7 docs.

--
assignee:  - docs@python
components: +Documentation -Library (Lib)
nosy: +docs@python
status: closed - open

___
Python tracker rep...@bugs.python.org
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

[Berker Peksag]

Changes by Berker Peksag berker.pek...@gmail.com:


--
keywords: +easy
stage: resolved - needs patch

___
Python tracker rep...@bugs.python.org
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

[R. David Murray]

R. David Murray added the comment:

The API is what it is.  In the Python3 docs this is documented as a backward 
compatibility issue, and the workaround using the new errors.codes is provided. 
 For 2.7 we are stuck with what we have, since we don't add new features to 2.7.

--
nosy: +r.david.murray
resolution:  - wont fix
stage:  - resolved
status: open - closed

___
Python tracker rep...@bugs.python.org
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

[Björn Karge]

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 rep...@bugs.python.org
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

[Björn Karge]

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 rep...@bugs.python.org
http://bugs.python.org/issue23019
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com