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 ncoghlan
Recipients benjamin.peterson, lemburg, meador.inge, ncoghlan, serhiy.storchaka, vstinner
Date 2013-11-07.12:23:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
After thinking about this some more, perhaps a -3 warning in 2.7 would be a
better solution? That would be more robust, as it could complain any time
unicode.encode produced unicode and str.decode produced str and point users
to the codecs module level functions as a forward compatible alternative.

Producing Py3k warnings when calling unicode.decode and str.encode under -3
would also be appropriate (although those warnings may already exist).
Date User Action Args
2013-11-07 12:23:12ncoghlansetrecipients: + ncoghlan, lemburg, vstinner, benjamin.peterson, meador.inge, serhiy.storchaka
2013-11-07 12:23:12ncoghlanlinkissue17823 messages
2013-11-07 12:23:12ncoghlancreate