Serhiy Storchaka added the comment:
It looks rather as a bug in C code. There is no need to return Py_ssize_t
instead of int.
--
nosy: +serhiy.storchaka
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22580
STINNER Victor added the comment:
It looks rather as a bug in C code. There is no need to return Py_ssize_t
instead of int.
Oh yes, you're right. A Py_ssize_t to return -1, 0 or 1 is overkill :-)
But PyUnicode_Tailmatch() is now part of the stable ABI, the inefficient return
type is not a
Roundup Robot added the comment:
New changeset 4aba14bb6b1e by Victor Stinner in branch '3.4':
Closes #22580: Fix documentation of PyUnicode_Tailmatch()
https://hg.python.org/cpython/rev/4aba14bb6b1e
New changeset 335d16d864e1 by Victor Stinner in branch 'default':
(Merge 3.4) Closes #22580:
Roundup Robot added the comment:
New changeset de4ffe20 by Victor Stinner in branch '2.7':
Closes #22580: Fix documentation of PyUnicode_Tailmatch()
https://hg.python.org/cpython/rev/de4ffe20
--
___
Python tracker rep...@bugs.python.org
STINNER Victor added the comment:
The documentation for PyUnicode_Tailmatch says it returns an int
It's an old bug (since Python 2.7 or older) and it is now fixed. Thanks for the
report Josh.
--
___
Python tracker rep...@bugs.python.org
New submission from Josh Ayers:
The documentation for PyUnicode_Tailmatch says it returns an int:
https://docs.python.org/3/c-api/unicode.html?highlight=pyunicode_tailmatch#c.PyUnicode_Tailmatch
However, the include file shows it returns Py_ssize_t:
