This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients Timothée.CEZARD, eric.araujo, loewis, serhiy.storchaka
Date 2016-01-16.17:51:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1452966667.81.0.179850764888.issue9006@psf.upfronthosting.co.za>
In-reply-to
Content
xmlrpc uses XML. This format includes information about the encoding and doesn't need external specification.

The server in the example is not correct. It generates XML with default XML declaration that implies the UTF-8 encoding, but the body is encoded with non-UTF-8 encoding. If add the argument encoding='UTF-8' the example works.

But this feature is not covered by tests. Proposed patch adds tests for non-default client and server encodings. No changes for the xmlrpc module itself is needed.
History
Date User Action Args
2016-01-16 17:51:07serhiy.storchakasetrecipients: + serhiy.storchaka, loewis, eric.araujo, Timothée.CEZARD
2016-01-16 17:51:07serhiy.storchakasetmessageid: <1452966667.81.0.179850764888.issue9006@psf.upfronthosting.co.za>
2016-01-16 17:51:07serhiy.storchakalinkissue9006 messages
2016-01-16 17:51:07serhiy.storchakacreate