Message 332209 - 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	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	<1545302936.41.0.788709270274.issue35544@psf.upfronthosting.co.za>
In-reply-to

Content
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 :)

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 :)

History
Date	User	Action	Args
2018-12-20 10:48:56	radiocane	set	recipients: + radiocane, lemburg, vstinner, ezio.melotti, steven.daprano, serhiy.storchaka
2018-12-20 10:48:56	radiocane	set	messageid: <1545302936.41.0.788709270274.issue35544@psf.upfronthosting.co.za>
2018-12-20 10:48:56	radiocane	link	issue35544 messages
2018-12-20 10:48:56	radiocane	create