➜

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 lemburg
Recipients benjamin.peterson, docs@python, ezio.melotti, lemburg, martin.panter, mdk, r.david.murray, serhiy.storchaka, toonarmycaptain, vstinner
Date 2018-11-04.22:02:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1541368969.49.0.788709270274.issue31873@psf.upfronthosting.co.za>
In-reply-to
Content 
If you want to do this correctly, you have to check each case:

* if "unicode object" refers to a C PyUnicode object, it's probably better to use "PyUnicode object"
* if "unicode object" refers to a C PyObject object, with type "unicode", it's probably better to leave it as is
* if "unicode object" refers to a Python unicode object, it's probably better to call it "Unicode string object" or just "string object" in Python 3
* if "unicode object" does not indicate whether Python or C is meant, "Unicode object" is probably better
History
Date User Action Args
2018-11-04 22:02:49lemburgsetrecipients: + lemburg, vstinner, benjamin.peterson, ezio.melotti, r.david.murray, docs@python, martin.panter, serhiy.storchaka, mdk, toonarmycaptain
2018-11-04 22:02:49lemburgsetmessageid: <1541368969.49.0.788709270274.issue31873@psf.upfronthosting.co.za>
2018-11-04 22:02:49lemburglinkissue31873 messages
2018-11-04 22:02:49lemburgcreate