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 terry.reedy
Recipients docs@python, ezio.melotti, ohnobinki, terry.reedy
Date 2010-05-14.19:34:32
SpamBayes Score 0.00040769967
Marked as misclassified No
Message-id <1273865674.33.0.60735603335.issue8694@psf.upfronthosting.co.za>
In-reply-to
Content
Yes, the faq entry has example code like
 "value = unicode(value, "utf-8")"
This whole section now applies when 'value' is a bytes or bytearray object and one calls str(value).

For portability, one should in 2.6/7 use unicode strings as much as possible and the bytes and unicode functions but not the str function. Then 2to3.py will change 'unicode' to 'str'. This should be a separate FAQ entry (if not already), for both 2.x and 3.x, with more complete advice from MLV (from whom I am parroting the above).
History
Date User Action Args
2010-05-14 19:34:34terry.reedysetrecipients: + terry.reedy, ezio.melotti, docs@python, ohnobinki
2010-05-14 19:34:34terry.reedysetmessageid: <1273865674.33.0.60735603335.issue8694@psf.upfronthosting.co.za>
2010-05-14 19:34:32terry.reedylinkissue8694 messages
2010-05-14 19:34:32terry.reedycreate