Author mforkel
Recipients mforkel
Date 2020-01-31.18:26:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1580495168.43.0.888386577415.issue39512@roundup.psfhosted.org>
In-reply-to
Content
xmlrpc uses expat, which is not XML 1.1 compliant. Therefore, when transferring text, some characters which a valid according to the XML-RPC specification (http://xmlrpc.com/spec.md) will trigger expat to raise xml.parsers.expat.ExpatError: not well-formed (invalid token) exceptions.

Issue 11804 (https://bugs.python.org/issue11804) which reported this problem has been closed almost 20 years ago, referencing an expat bug report for XML 1.1 support. That bug report is still open and there is no current plan to support XML 1.1 in expat (https://github.com/libexpat/libexpat/issues/378#issuecomment-578914067).

I would like to suggest to replace expat as the default parser in xmlrpc or at least make it easier to override the default (see https://bugs.python.org/issue6701).
History
Date User Action Args
2020-01-31 18:26:08mforkelsetrecipients: + mforkel
2020-01-31 18:26:08mforkelsetmessageid: <1580495168.43.0.888386577415.issue39512@roundup.psfhosted.org>
2020-01-31 18:26:08mforkellinkissue39512 messages
2020-01-31 18:26:08mforkelcreate