[Python-Dev] r84430 - in python/branches/py3k: Include/unicodeobject.h Objects/unicodeobject.c (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Fri Sep 3 12:52:51 CEST 2010
- Previous message: [Python-Dev] r84430 - in python/branches/py3k: Include/unicodeobject.h Objects/unicodeobject.c
- Next message: [Python-Dev] r84430 - in python/branches/py3k: Include/unicodeobject.h Objects/unicodeobject.c
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Sep 3, 2010 at 8:14 PM, Victor Stinner <victor.stinner at haypocalc.com> wrote:
Le vendredi 03 septembre 2010 11:20:04, vous avez écrit :
> But I didn't found any doc for other PyUNICODEstr*() > functions in Doc/c-api/*.rst.
http://bugs.python.org/issue8649 - PyUNICODE* functions are undocumented Opened since 3 months. It looks like programmers don't like writing documentation :-)
In this case, "C programmers think C stdlib function names are intuitive" may be closer to the mark ;)
Cheers, Nick.
P.S. More seriously, these particular functions really are just like the standard C function of the same name, only operating on Py_UNICODE* rather than char*, so I can understand documentation being skipped when they were added. However, they may as well be mentioned in http://docs.python.org/dev/c-api/unicode.html#plain-py-unicode
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message: [Python-Dev] r84430 - in python/branches/py3k: Include/unicodeobject.h Objects/unicodeobject.c
- Next message: [Python-Dev] r84430 - in python/branches/py3k: Include/unicodeobject.h Objects/unicodeobject.c
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]