➜

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 vstinner
Recipients docs@python, eric.araujo, fdrake, lemburg, mark.dickinson, pitrou, vstinner
Date 2010-06-11.23:37:50
SpamBayes Score 0.00046760959
Marked as misclassified No
Message-id <1276299471.66.0.980607607084.issue8939@psf.upfronthosting.co.za>
In-reply-to
Content 
"PyUnicodeObject*" is not the best choice for the description of the function, and I don't really like "PyUnicode". Can't we use C types in the function prototype and Python types in the description?

Example:
-------
s (PyUnicodeObject* or None) [char *]
Convert a null-terminated C string to a Python unicode object using 'utf-8' encoding. If the C string pointer is NULL, None is used.
-----
PyUnicodeObject will be a link to the C type, and unicode a link to the  Python type.
History
Date User Action Args
2010-06-11 23:37:51vstinnersetrecipients: + vstinner, lemburg, fdrake, mark.dickinson, pitrou, eric.araujo, docs@python
2010-06-11 23:37:51vstinnersetmessageid: <1276299471.66.0.980607607084.issue8939@psf.upfronthosting.co.za>
2010-06-11 23:37:50vstinnerlinkissue8939 messages
2010-06-11 23:37:50vstinnercreate