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 ezio.melotti
Recipients brianvanderburg2, docs@python, ezio.melotti, r.david.murray, scoder, serhiy.storchaka, upendra-k14
Date 2016-01-09.13:29:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1452346196.03.0.730217622485.issue18911@psf.upfronthosting.co.za>
In-reply-to
Content
> On Python 3 you should not only open file in text mode with specified
> encoding, but also specify the "xmlcharrefreplace" error handler.

Isn't this only required in case there are non encodable characters?
If the encoding is utf-8, this shouldn't be necessary (unless there are lone surrogates).  Specifying xmlcharrefreplace might be useful while using ascii or latin1 though.

The docs of writexml don't seem to specify if the file should be opened in text or binary mode but istm that only text mode is supported.  The advice of using xmlcharrefreplace could be added in a note.
History
Date User Action Args
2016-01-09 13:29:56ezio.melottisetrecipients: + ezio.melotti, scoder, r.david.murray, docs@python, serhiy.storchaka, brianvanderburg2, upendra-k14
2016-01-09 13:29:56ezio.melottisetmessageid: <1452346196.03.0.730217622485.issue18911@psf.upfronthosting.co.za>
2016-01-09 13:29:56ezio.melottilinkissue18911 messages
2016-01-09 13:29:55ezio.melotticreate