[issue32582] chr raises OverflowError

Change by Mark Dickinson : -- nosy: +mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32582] chr raises OverflowError

Change by Alex Waygood : -- type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32582] chr raises OverflowError

Irit Katriel added the comment: Still raising OVerflowError on 3.11: >>> print(chr(0x8000)) Traceback (most recent call last): File "", line 1, in OverflowError: Python int too large to convert to C int -- nosy: +iritkatriel versions: +Python 3.11 -Python 3.7

[issue32582] chr raises OverflowError

Serhiy Storchaka added the comment: Perhaps this issue should be raised on Python-Dev, since it changes the old and well-known behavior of buildins. I think that ValueError is more appropriate, but in past we decided to keep OverflowError for compatibility. If

[issue32582] chr raises OverflowError

Terry J. Reedy added the comment: The message I get on Windows is OverflowError: Python int too large to convert to C long Given that the exception type is documented, making this a clear bug, I would be tempted to fix in 3.6 also. But your decision. -- nosy:

[issue32582] chr raises OverflowError

STINNER Victor added the comment: It's more an implementation issue. I proposed PR 5218 to also raise a ValueError on overflow. I propose to only change Python 3.7, and only Python 2.7 and 3.6 unchanged. -- nosy: +vstinner versions: +Python 3.7 -Python 3.6

[issue32582] chr raises OverflowError

Change by STINNER Victor : -- pull_requests: +5071 stage: -> patch review ___ Python tracker ___

[issue32582] chr raises OverflowError

New submission from Uwe Kleine-König : Hello, the description for chr (from https://docs.python.org/3/library/functions.html#chr) reads as: Return the string representing a character whose Unicode code point is the integer i. [...] The valid range