[issue10108] ExpatError not property wrapped

Change by Joannah Nanjekye : -- nosy: +nanjekyejoannah ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue10108] ExpatError not property wrapped

Stefan Behnel added the comment: I agree that it's surprising to get a low-level parser error from a high-level library like xmlrpc. I think this can be changed without deprecation, because users must expect exceptions from the xmlrpc library in any case. Targeting to Py3.9, needs patch with

[issue10108] ExpatError not property wrapped

Stéphane Wirtel added the comment: Hi Scoder, I am not sure if this issue is relevant for 3.7 and 3.8 but do you want to check this issue? Thank you, -- nosy: +matrixise, scoder versions: +Python 3.7, Python 3.8 -Python 3.1 ___ Python tracker

[issue10108] ExpatError not property wrapped

Changes by Fred L. Drake, Jr. : -- nosy: +fdrake ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue10108] ExpatError not property wrapped

Changes by Éric Araujo : -- nosy: +d...@python versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.6 ___ Python tracker ___ ___ Py

[issue10108] ExpatError not property wrapped

Leo Shklovskii added the comment: I'm sorry, I would like to but I don't have the time in the near future. I'm running into this as a secondary symptom of a bigger issue (in our own setup, not in Python) that I'm troubleshooting. -- ___ Python trac

[issue10108] ExpatError not property wrapped

Martin v. Löwis added the comment: Not necessarily a separate report. Would you be interested in writing a patch that clears that all up (for 2.7 and/or 3.2)? -- ___ Python tracker ___

[issue10108] ExpatError not property wrapped

Leo Shklovskii added the comment: Looking at the docs more closely, you're right, I'm not entirely sure what error should come out in that case but my main point with the bug is that the error should be an xmlrpclib error rather than one from the specific parser that its choosing to use. Sho

[issue10108] ExpatError not property wrapped

Martin v. Löwis added the comment: > From my understanding of the documentation, the expected behavior > is for xmlrpclib to raise an xmlrpclib.Fault [...] What specific wording in the documentation makes you thinks so? If anything, I'd expect a ResponseError (which appears undocumented). ---

[issue10108] ExpatError not property wrapped

New submission from Leo Shklovskii : >From my understanding of the documentation, the expected behavior is for >xmlrpclib to raise an xmlrpclib.Fault wrapping the original error from >whatever parser it chose to use if there's an error in parsing the response. If, however, its using Expat unde