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 effbot
Recipients effbot, flox, georg.brandl, gvanrossum, r.david.murray, scoder
Date 2010-03-12.10:22:39
SpamBayes Score 0.00121247
Marked as misclassified No
Message-id <1268389361.54.0.405869928108.issue8047@psf.upfronthosting.co.za>
In-reply-to
Content
"I wouldn't raise much opposition against tobytes() as an alias for tostring(), although that sounds more like duplicating an otherwise simple API."

Adding an alias would be a way address the 2.X/3.X terminology overlap; string traditionally implies 8-bit in 2.X, and apparently now Unicode in 3.X.  That's likely to cause a lot of confusion for people switching over (and to people writing 3.X documentation, as well; the array module's documentation is an example).

ET isn't the only thing with tostring functionality, of course -- it's  pretty much the standard name for "serialize data structure to byte string for later transmission" -- so it probably wouldn't hurt with a python-dev pronouncement here.
History
Date User Action Args
2010-03-12 10:23:17effbotunlinkissue8047 messages
2010-03-12 10:22:41effbotsetrecipients: + effbot, gvanrossum, georg.brandl, scoder, r.david.murray, flox
2010-03-12 10:22:41effbotsetmessageid: <1268389361.54.0.405869928108.issue8047@psf.upfronthosting.co.za>
2010-03-12 10:22:40effbotlinkissue8047 messages
2010-03-12 10:22:40effbotcreate