A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2010-September/103423.html below:

[Python-Dev] r84430 - in python/branches/py3k: Include/unicodeobject.h Objects/unicodeobject.c

[Python-Dev] r84430 - in python/branches/py3k: Include/unicodeobject.h Objects/unicodeobject.cNick Coghlan ncoghlan at gmail.com
Fri Sep 3 12:52:51 CEST 2010
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 Py_UNICODE_str*()
>> > functions in Doc/c-api/*.rst.
>>
>> http://bugs.python.org/issue8649 - Py_UNICODE_* 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
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4