[issue13341] Incorrect documentation for "u" PyArg_Parse format unit
New submission from Ilya Novoselov ilya.novoselov@gmail.com:
Documentation states that u format unit returns "buffer of 16-bit Unicode (UTF-16) data" while it returns pointer to internal buffer of unicode data, which is either UCS-16 or UCS-32
http://docs.python.org/c-api/arg.html
---------- assignee: docs@python components: Documentation, Unicode messages: 147002 nosy: Ilya.Novoselov, docs@python, ezio.melotti priority: normal severity: normal status: open title: Incorrect documentation for "u" PyArg_Parse format unit type: behavior versions: Python 2.7
_______________________________________ Python tracker report@bugs.python.org http://bugs.python.org/issue13341 _______________________________________
STINNER Victor victor.stinner@haypocalc.com added the comment:
Can you write a patch?
---------- nosy: +haypo
_______________________________________ Python tracker report@bugs.python.org http://bugs.python.org/issue13341 _______________________________________
Ilya Novoselov ilya.novoselov@gmail.com added the comment:
No, I don't feel like I'm up to standard yet.
----------
_______________________________________ Python tracker report@bugs.python.org http://bugs.python.org/issue13341 _______________________________________
Changes by Mike Hoy mhoy09@gmail.com:
---------- nosy: +mikehoy
_______________________________________ Python tracker report@bugs.python.org http://bugs.python.org/issue13341 _______________________________________
Changes by Éric Araujo merwok@netwok.org:
---------- nosy: +loewis
_______________________________________ Python tracker report@bugs.python.org http://bugs.python.org/issue13341 _______________________________________
Changes by Mike Hoy mhoy09@gmail.com:
---------- nosy: -mikehoy
_______________________________________ Python tracker report@bugs.python.org http://bugs.python.org/issue13341 _______________________________________
Martin Panter added the comment:
The Python 3 documentation was updated in Issue 8593 (revision 5d4a5655575f). Perhaps some of the wording also applies to Python 2 and you can just copy it.
---------- nosy: +vadmium
_______________________________________ Python tracker report@bugs.python.org http://bugs.python.org/issue13341 _______________________________________
Joannah Nanjekye nanjekyejoannah@gmail.com added the comment:
This is has taken years but am curious, are we allowed to patch Python 2 given its EOL is almost due.
---------- nosy: +nanjekyejoannah
_______________________________________ Python tracker report@bugs.python.org https://bugs.python.org/issue13341 _______________________________________
STINNER Victor vstinner@python.org added the comment:
I don't think that it's still worth it to update Python 2 documentation at this point. I suggest to focus on enhancement of the Python 3 documentation instead.
----------
_______________________________________ Python tracker report@bugs.python.org https://bugs.python.org/issue13341 _______________________________________
Change by Irit Katriel iritkatriel@yahoo.com:
---------- resolution: -> out of date stage: -> resolved status: open -> closed
_______________________________________ Python tracker report@bugs.python.org https://bugs.python.org/issue13341 _______________________________________
participants (7)
-
Ilya Novoselov -
Irit Katriel
-
Joannah Nanjekye
-
Martin Panter
-
Mike Hoy
-
STINNER Victor
-
Éric Araujo