Message 187630 - Python tracker

➜

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	flox
Recipients	barry, belopolsky, benjamin.peterson, cben, eric.araujo, ezio.melotti, flox, georg.brandl, gvanrossum, jcea, lemburg, loewis, ncoghlan, pconnell, petri.lehtinen, ssbarnea, vstinner
Date	2013-04-23.12:05:43
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1366718743.44.0.808720144415.issue7475@psf.upfronthosting.co.za>
In-reply-to

Content
Another rant, because it matters to many of us: http://lucumr.pocoo.org/2012/8/11/codec-confusion/ IMHO, the solution to restore str.decode and bytes.encode and return TypeError for improper use is probably the most obvious for the average user.

Another rant, because it matters to many of us:
http://lucumr.pocoo.org/2012/8/11/codec-confusion/

IMHO, the solution to restore str.decode and bytes.encode and return TypeError for improper use is probably the most obvious for the average user.

History
Date	User	Action	Args
2013-04-23 12:05:43	flox	set	recipients: + flox, lemburg, gvanrossum, loewis, barry, georg.brandl, jcea, cben, ncoghlan, belopolsky, vstinner, benjamin.peterson, ezio.melotti, eric.araujo, ssbarnea, petri.lehtinen, pconnell
2013-04-23 12:05:43	flox	set	messageid: <1366718743.44.0.808720144415.issue7475@psf.upfronthosting.co.za>
2013-04-23 12:05:43	flox	link	issue7475 messages
2013-04-23 12:05:43	flox	create