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 r.david.murray
Recipients effbot, flox, georg.brandl, pitrou, r.david.murray, scoder
Date 2010-03-12.00:14:23
SpamBayes Score 0.00053314265
Marked as misclassified No
Message-id <>
Well, Benjamin pointed out to me that it would be a bad thing if array.tostring produced a string.  True, the method is named wrong, but it is less broken than returning a string.  I suspect that that is the same argument Fredrik is making: that returning the XML as a byte string is less broken than returning it as a string when it in fact may contain other encoded stuff.  The email package has some of the same problems, and there we are retooling the API to deal with this.

Presumably ET needs to have a retooled API for Python3 as well.  Then the question becomes what do we do in the meantime?  For email, we are just living with the breakage until we can get something better in place, because no one has come up with any good short term solutions for email.
Date User Action Args
2010-03-12 00:14:25r.david.murraysetrecipients: + r.david.murray, effbot, georg.brandl, pitrou, scoder, flox
2010-03-12 00:14:24r.david.murraysetmessageid: <>
2010-03-12 00:14:23r.david.murraylinkissue8047 messages
2010-03-12 00:14:23r.david.murraycreate