Serhiy Storchaka added the comment: I agree that the inconsistency should be fixed. But I'm not sure that we should use the words "an Unicode object" in Python 3. In many similar cases ("a bytes object", "a type object", "a module object") the name of Python type is used. "unicode" was a name of Python type in Python 2. In Python 3 it is "str". The term "Unicode string" also is widely used. Should not we use "a str object", "a string object", "a Unicode string" or "a Unicode string object" in the C API documentation? ---------- components: +Unicode nosy: +benjamin.peterson, ezio.melotti, haypo, lemburg, martin.panter, r.david.murray, serhiy.storchaka stage: -> patch review versions: +Python 3.6, Python 3.7 _______________________________________ Python tracker https://bugs.python.org/issue31873 _______________________________________

David Antonini added the comment: Does the Unicode documentation currently conform to that convention, or does it require editing? It appears to me that a lot of cases where reference to "Unicode object" is currently capitalised (most of them, in fact) may need to be modified. However, it would seem that there is a grey area in making a distinction between reference to the unicode type as implemented in Python and reference to the standard as a descriptor of the format of an object? The way I read there a lot of the cases are in essence a reference to both. ---------- _______________________________________ Python tracker https://bugs.python.org/issue31873 _______________________________________

Julien Palard added the comment: Currently in our documentation there's 89 "Unicode obj" vs 8 "unicode obj" so I'll go for it. ---------- nosy: +mdk _______________________________________ Python tracker https://bugs.python.org/issue31873 _______________________________________

Julien Palard added the comment: New changeset 85225b6a58a516c50c055d5114668ed2fcdcda8c by Julien Palard (toonarmycaptain) in branch 'master': bpo-31873: Update unicode.rst - 'unicode' capitalization (GH-4125) https://github.com/python/cpython/commit/85225b6a58a516c50c055d5114668ed2fcd... ---------- _______________________________________ Python tracker https://bugs.python.org/issue31873 _______________________________________

Julien Palard added the comment: I merged it, it's a small change that is consistent enough for me with the rest of the file and the doc. Marc-Andre is right though, and if anyone have the courage, the whole doc should be proofread to update accordingly, but let's make it a whole other PR. Thanks David for your contribution and sorry for the delay. ---------- resolution: -> fixed stage: patch review -> resolved status: open -> closed _______________________________________ Python tracker https://bugs.python.org/issue31873 _______________________________________