Calling PyLong_FromString(str, NULL, 0) fails, if str is a string containing a decimal number with leading zeros, even though such strings should be parsed as decimal numbers according to the documentation:

"If base is 0, the radix will be determined based on the leading characters of str: if str starts with '0x' or '0X', radix 16 will be used; if str starts with '0o' or '0O', radix 8 will be used; if str starts with '0b' or '0B', radix 2 will be used; otherwise radix 10 will be used"

Examples:
PyLong_FromString("15", NULL, 0); // Returns int(15) (Correct)
PyLong_FromString("0xF", NULL, 0); // Returns int(15) (Correct)
PyLong_FromString("015", NULL, 0); // Should return int(15), but raises ValueError: invalid literal for int() with base 0: '015'

Version information:
Python 3.5.2 (v3.5.2:4def2a2901a5, Jun 25 2016, 22:18:55) [MSC v.1900 64 bit (AMD64)] on win32

My guess is this is supposed to emulate (or is actually the implementation of) the "int" constructor and the Python syntax. In these cases, numbers with leading zeros are disallowed. This was to help with Python 2 porting, where a leading zero specified an octal number.

>>> 010
    010
      ^
SyntaxError: invalid token
>>> int("010", 0)
ValueError: invalid literal for int() with base 0: '010'

Maybe it is better to fix the documentation.

Yes, PyLong_FromString is directly used by the implementation of int, and is also used in parsing of numeric integer literals in source:

So I agree that this is a documentation bug. There's also no mention of the support for underscores in the documentation.

I have a pull request ready for the documentation, but I didn't understand the underscore usage, so I couldn't add that.

If you explain it, then I can try to add it.

String arguments to int are quoted int literals. From
https://docs.python.org/3/reference/lexical_analysis.html#literals
'Underscores are ignored for determining the numeric value of the literal. They can be used to group digits for enhanced readability. One underscore can occur between digits, and after base specifiers like 0x.'

For your patch, I would summarize this by expanding 'Leading spaces are ignored.' to the following (in patch comment also).
"Leading spaces and single underscores after a base specifier and between digits are ignored."

Thank you. I've added that change.

For the backporting, I think that would only be applicable to 3.6 and 3.7?

Underscores are only applicable to 3.6+, but the original concern about leading zeros applies to 3.5.

On Git Hub I suggested dropping the details and just referring to the Lexical Analysis section <https://docs.python.org/3.5/reference/lexical_analysis.html#integer-literals\> for the details.

FWIW here is my understanding of integer literals (with base=0):

• 0x10 => hexadecimal
• 0b10 => binary
• 0o10 => octal (corresponds to 010 in Python 2)
• 01 => illegal (avoids conflict with Python 2)
• 00 => zero (special case; was treated as octal zero in Python 2)
• 10 => decimal (must not start with digit 0)

If you want to spell out the rules, in my mind there are four special prefixes, 0x, 0b, 0o and 0, and the default is decimal if none of those prefixes apply.

New changeset 26896f2 by Mariatta (csabella) in branch 'master':
bpo-29751: Improve PyLong_FromString documentation (GH-915)
26896f2

New changeset d51d093 by Mariatta in branch '3.5':
[3.5] bpo-29751: Improve PyLong_FromString documentation (GH-915) (bpo-1267)
d51d093

New changeset ea0efa3 by Mariatta in branch '3.6':
[3.6] bpo-29751: Improve PyLong_FromString documentation (GH-915) (bpo-1266)
ea0efa3

New changeset 9eb5ca0 by Mariatta in branch 'master':
bpo-29751: add Cheryl Sabella to Misc/ACKS (GH-1268)
9eb5ca0

I merged the PR, backported it to 3.5 and 3.6, and added Cheryl to Misc/ACKS.

Thanks everyone :)

Oh, I didn't expect that. That is so cool! Thanks Mariatta. :-)