Created on 2020-01-31 18:26 by mforkel, last changed 2020-02-09 19:48 by terry.reedy.
| Messages (2) | |||
|---|---|---|---|
| msg361124 - (view) | Author: Malte Forkel (mforkel) | Date: 2020-01-31 18:26 | |
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). |
|||
| msg361660 - (view) | Author: Terry J. Reedy (terry.reedy) *  |
Date: 2020-02-09 19:48 | |
Stefen, do you know anything about this? There is no coredev expert for xmlrpc. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2020-02-09 19:48:49 | terry.reedy | set | nosy:
+ terry.reedy, scode messages: + msg361660 title: expat parser not xml 1.1 (breaks xmlrpclib) - still -> expat parser not xml 1.1 compliant (breaks xmlrpclib) - still |
| 2020-01-31 18:26:08 | mforkel | create | |