[issue21546] int('\0') gives wrong error message

Changes by Terry J. Reedy : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> `int()`, `float()`, etc think python strings are null-terminated type: -> behavior ___ Python tracker

[issue21546] int('\0') gives wrong error message

eryksun added the comment: See issue 16741. This is fixed in 3.3, but 2.7 intentionally keeps the old behavior. -- nosy: +eryksun ___ Python tracker ___

[issue21546] int('\0') gives wrong error message

STINNER Victor added the comment: It looks like the issue was already fixed in Python 3: Python 3.5.0a0 (default:61d9aa8be445, May 20 2014, 16:03:51) >>> int('a') Traceback (most recent call last): File "", line 1, in ValueError: invalid literal for int() with base 10: 'a' >>> int('\0a') Tra

[issue21546] int('\0') gives wrong error message

New submission from Kurt Rose: int() ignores everything after a null byte when reporting an error message. Here you can see an example of how this manifests, and why could be a problem. Python 2.7.6 (default, Nov 10 2013, 19:24:18) [MSC v.1500 32 bit(Intel)] on win32 Type "help", "copyright",