[issue44267] Wrong PEP 515 parsing in decimal module (both C and Python versions)

Sergey B Kirpichev added the comment: On Sun, May 30, 2021 at 08:58:56AM +, Mark Dickinson wrote: > Yep, you're absolutely right. I should have said "after the PEP is final" Unfortunately, neither correction can fix that the PEP does not "accurately describes the state of the

[issue44267] Wrong PEP 515 parsing in decimal module (both C and Python versions)

Change by Mark Dickinson : -- resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue44267] Wrong PEP 515 parsing in decimal module (both C and Python versions)

Mark Dickinson added the comment: > Regarding mail thread: I don't think that following the PEP will slow down string conversion. Sorry, I just don't think it's worth re-opening this discussion; Stefan Krah had good reasons (not just speed) to avoid implementing a precise interpretation of

[issue44267] Wrong PEP 515 parsing in decimal module (both C and Python versions)

Mark Dickinson added the comment: > Well, then I something misunderstood in PEP 0 Yep, you're absolutely right. I should have said "after the PEP is final", not "after the PEP is accepted". PEP 515 was marked final on April 28th, 2017. > The current behaviour is documented. Thanks; I

[issue44267] Wrong PEP 515 parsing in decimal module (both C and Python versions)

Sergey B Kirpichev added the comment: On Sun, May 30, 2021 at 08:32:40AM +, Mark Dickinson wrote: > Standards Track PEPs are historical documents; it's quite common that an > actual implementation ends up diverging from a PEP in small ways after > the PEP is accepted, and we don't usually

[issue44267] Wrong PEP 515 parsing in decimal module (both C and Python versions)

Mark Dickinson added the comment: > If this is not a bug - it should be adjusted Standards Track PEPs are historical documents; it's quite common that an actual implementation ends up diverging from a PEP in small ways after the PEP is accepted, and we don't usually do post-hoc updates in

[issue44267] Wrong PEP 515 parsing in decimal module (both C and Python versions)

Sergey B Kirpichev added the comment: On Sun, May 30, 2021 at 08:20:14AM +, Mark Dickinson wrote: > There was some discussion of this on the python-dev mailing list at the time I see. > It's probably best left alone. PEP 515 is clear. If this is not a bug - it should be adjusted (as it

[issue44267] Wrong PEP 515 parsing in decimal module (both C and Python versions)

Mark Dickinson added the comment: There was some discussion of this on the python-dev mailing list at the time - see https://mail.python.org/pipermail/python-dev/2016-March/143556.html and the surrounding thread. It's probably best left alone. --

[issue44267] Wrong PEP 515 parsing in decimal module (both C and Python versions)

Change by Sergey B Kirpichev : Added file: https://bugs.python.org/file50072/0001-bpo-44267-fix-parsing-Decimal-s-with-underscores.patch ___ Python tracker ___

[issue44267] Wrong PEP 515 parsing in decimal module (both C and Python versions)

Change by Karthikeyan Singaravelan : -- nosy: +facundobatista, mark.dickinson, rhettinger ___ Python tracker ___ ___

[issue44267] Wrong PEP 515 parsing in decimal module (both C and Python versions)

New submission from Sergey B Kirpichev : While working on issue44258 I discover that the decimal module doesn't follow specification in PEP 515: "The current proposal is to allow one underscore between digits, and after base specifiers in numeric literals." (c) For example: >>>