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 matheus.v.portela
Recipients BreamoreBoy, docs@python, ezio.melotti, matheus.v.portela, serhiy.storchaka, vstinner
Date 2015-08-31.23:03:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Just checking, it would be required to update Objects/unicodeobject.c, Include/unicodeobject.h, and Doc/c-api/unicode.rst, right?

As far as I saw, "unicode" means a Python object with unicode string, "u" is a UTF-8 encoded C string, "str" and "s" are encoded C strings (UTF-8, UTF-7, ASCII, Latin-1, among others). Is it alright to rename Python unicode objects to "unicode" and the others to simply "str"? These names are more meaningful than the single character alternatives.

The same logic would be applied to the other types, always keeping the longer name rather than the single character ones.
Date User Action Args
2015-08-31 23:03:57matheus.v.portelasetrecipients: + matheus.v.portela, vstinner, ezio.melotti, docs@python, BreamoreBoy, serhiy.storchaka
2015-08-31 23:03:57matheus.v.portelasetmessageid: <>
2015-08-31 23:03:57matheus.v.portelalinkissue18697 messages
2015-08-31 23:03:56matheus.v.portelacreate