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 ncoghlan
Recipients benjamin.peterson, ezio.melotti, lemburg, ncoghlan, pitrou, pje, serhiy.storchaka, vstinner
Date 2014-08-24.15:23:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1408893784.05.0.955314394792.issue22264@psf.upfronthosting.co.za>
In-reply-to
Content
Current cryptic incantation that requires deep knowledge of the encoding system to follow:

    data = data.encode("latin-1").decode("utf-8", "surrogateescape")

Replacement that is not only more self-documenting, but also gives you something specific to look up in order to learn more:

    data = wsgiref.util.fix_encoding(data, "utf-8")

As a WSGI server, the standard library code mostly does this in the other direction, converting data from its original web server provided encoding *to* latin-1.
History
Date User Action Args
2014-08-24 15:23:04ncoghlansetrecipients: + ncoghlan, lemburg, pje, pitrou, vstinner, benjamin.peterson, ezio.melotti, serhiy.storchaka
2014-08-24 15:23:04ncoghlansetmessageid: <1408893784.05.0.955314394792.issue22264@psf.upfronthosting.co.za>
2014-08-24 15:23:04ncoghlanlinkissue22264 messages
2014-08-24 15:23:03ncoghlancreate