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 radiocane
Recipients ezio.melotti, lemburg, radiocane, serhiy.storchaka, steven.daprano, vstinner
Date 2018-12-20.10:48:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Given that:
1) No standard codec returns unicode
2) I consider as "most common scenario" the case where a user wants to encode a unicode object using some character encoding and get back an str-like object

I'll keep on finding "-> string or unicode" misleading. I'd rather have the same as str.encode i.e. "-> object".
Anyway thanks for your time and attention :)
Date User Action Args
2018-12-20 10:48:56radiocanesetrecipients: + radiocane, lemburg, vstinner, ezio.melotti, steven.daprano, serhiy.storchaka
2018-12-20 10:48:56radiocanesetmessageid: <>
2018-12-20 10:48:56radiocanelinkissue35544 messages
2018-12-20 10:48:56radiocanecreate