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 Guillaume.Bouchard, chris.jerdonek, docs@python, eric.araujo, ezio.melotti, pitrou, r.david.murray, terry.reedy
Date 2012-10-15.11:05:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1350299110.51.0.674960545785.issue13538@psf.upfronthosting.co.za>
In-reply-to
Content
Instead of documenting what *encoding* and *errors* do, I would just say that str(bytesobj, encoding, errors) is equivalent to bytesobj.decode(encoding, errors) (assuming it really is).  I don't like encodings/decodings done via the str/bytes constructors, and I think the docs should encourage the use of bytes.decode/str.encode.
History
Date User Action Args
2012-10-15 11:05:10ezio.melottisetrecipients: + ezio.melotti, terry.reedy, pitrou, eric.araujo, r.david.murray, chris.jerdonek, docs@python, Guillaume.Bouchard
2012-10-15 11:05:10ezio.melottisetmessageid: <1350299110.51.0.674960545785.issue13538@psf.upfronthosting.co.za>
2012-10-15 11:05:10ezio.melottilinkissue13538 messages
2012-10-15 11:05:10ezio.melotticreate