incorrect return values of optimised builtin functions/methods

[robertwb]

In Python, calls to setattr() or some_list.sort() return None. When optimised in Cython, they return 0 on success or -1 on error instead. The 0 return value is visible to user code.

Plus, Cython currently fails to handle the return value in some cases, so using the return value as Python object can crash as the value may not even get coerced.

This was found in a CPython unit test which tests the return value.

Migrated from http://trac.cython.org/ticket/688

[robertwb]

scoder changed description from

In Python, some_list.sort() returns None. When optimised in Cython, it returns 0 on success or -1 on error instead.

Plus, Cython currently fails completely to handle the return value, so using the return value as Python object crashes as the value does not even get coerced.

This was found in a CPython unit test which tests the return value.

to

In Python, calls to setattr() or some_list.sort() return None. When optimised in Cython, they return 0 on success or -1 on error instead. The 0 return value is visible to user code.

Plus, Cython currently fails to handle the return value in some cases, so using the return value as Python object can crash as the value may not even get coerced.

This was found in a CPython unit test which tests the return value.
summary from

incorrect return values of optimised builtin methods like list.sort()

to

incorrect return values of optimised builtin functions/methods
commented

[robertwb]

scoder changed owner to scoder
status from new to assigned
commented

[robertwb]

scoder changed milestone from wishlist to 0.15
resolution to fixed
status from assigned to closed
commented

Fixed here:

bba74d8