Skip to content

Comments

[3.11] gh-115011: Improve support of __index__() in setters of members with unsigned integer type (GH-115029)#115295

Merged
serhiy-storchaka merged 1 commit intopython:3.11from
serhiy-storchaka:backport-d9d6909-3.11
Feb 11, 2024
Merged

[3.11] gh-115011: Improve support of __index__() in setters of members with unsigned integer type (GH-115029)#115295
serhiy-storchaka merged 1 commit intopython:3.11from
serhiy-storchaka:backport-d9d6909-3.11

Conversation

@serhiy-storchaka
Copy link
Member

@serhiy-storchaka serhiy-storchaka commented Feb 11, 2024

Setters for members with an unsigned integer type now support the same range of valid values for objects that has a index() method as for int.

Previously, Py_T_UINT, Py_T_ULONG and Py_T_ULLONG did not support objects that has a index() method larger than LONG_MAX.

Py_T_ULLONG did not support negative ints. Now it supports them and emits a RuntimeWarning.
(cherry picked from commit d9d6909)

…members with unsigned integer type (pythonGH-115029)

Setters for members with an unsigned integer type now support
the same range of valid values for objects that has a __index__()
method as for int.

Previously, Py_T_UINT, Py_T_ULONG and Py_T_ULLONG did not support
objects that has a __index__() method larger than LONG_MAX.

Py_T_ULLONG did not support negative ints. Now it supports them and
emits a RuntimeWarning.
(cherry picked from commit d9d6909)

Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant