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 effbot, flox, georg.brandl, gvanrossum, r.david.murray, scoder
Date 2010-03-22.09:09:28
SpamBayes Score 1.0929164e-08
Marked as misclassified No
Message-id <>
> Supporting unicode for lxml.etree compatibility is fine with me, but I
> think it might make sense to support the string "unicode" as well (as
> a pseudo-encoding -- it's pretty clear to me that nobody will ever
> define a real character encoding with that name :-).

The reason I chose the unicode type over a 'unicode' string name at the time was that I wanted to make a clear distinction to show that this is not just selecting a different codec but that it changes the output type.

I don't really care either way, though, given that this reads a lot less well in Py3. If ET supports both, lxml will follow.

Date User Action Args
2010-03-22 09:09:34scodersetrecipients: + scoder, gvanrossum, effbot, georg.brandl, r.david.murray, flox
2010-03-22 09:09:34scodersetmessageid: <>
2010-03-22 09:09:28scoderlinkissue8047 messages
2010-03-22 09:09:28scodercreate