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 scoder
Recipients Windson Yang, brianvanderburg2, docs@python, ezio.melotti, scoder, serhiy.storchaka, upendra-k14
Date 2019-05-31.10:58:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1559300286.03.0.124864502787.issue18911@roundup.psfhosted.org>
In-reply-to
Content
Asking users unconditionally to use the "xmlcharrefreplace" replacement method seems wrong for UTF-8. It should not be necessary.

We should, however, document explicitly that the file will receive text and not bytes, i.e. that users are themselves responsible for opening the output file with the desired encoding. We should also make it clearer that the "encoding" argument to writexml() does not change that.
History
Date User Action Args
2019-05-31 10:58:06scodersetrecipients: + scoder, ezio.melotti, docs@python, serhiy.storchaka, brianvanderburg2, upendra-k14, Windson Yang
2019-05-31 10:58:06scodersetmessageid: <1559300286.03.0.124864502787.issue18911@roundup.psfhosted.org>
2019-05-31 10:58:06scoderlinkissue18911 messages
2019-05-31 10:58:05scodercreate