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 Arfrever, ezio.melotti, ncoghlan, pitrou, r.david.murray, serhiy.storchaka, vstinner
Date 2014-08-24.11:46:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
That's why I think a function like redecode is a bad idea.
With Python 2 I've seen lot of people blindingly trying .decode when .encode failed (and the other way around) whenever they were getting an UnicodeError (and the fact that decoding Unicode results in an encode error didn't help).
I'm afraid that confused developers will try to (mis)use redecode as a workaround to attempt to fix something that shouldn't be broken in the first place, without actually understanding what the real problem is.
There's really no excuse for developers not to know Unicode nowadays (Joel Spolsky said the same thing more than 10 years ago).
IME people also tend to overestimate how difficult it is to understand Unicode.  While it is true that you can go pretty deep down the rabbit hole, the basic concepts necessary for everyday use are pretty simple and straightforward.
Date User Action Args
2014-08-24 11:46:14ezio.melottisetrecipients: + ezio.melotti, ncoghlan, pitrou, vstinner, Arfrever, r.david.murray, serhiy.storchaka
2014-08-24 11:46:14ezio.melottisetmessageid: <>
2014-08-24 11:46:14ezio.melottilinkissue18814 messages
2014-08-24 11:46:13ezio.melotticreate