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

[Sergey B Kirpichev]

Sergey B Kirpichev <skirpichev at gmail.com> added the comment:

On Sun, May 30, 2021 at 08:32:40AM +0000, 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 do post-hoc updates in those situations.

Well, then I something misunderstood in PEP 0:
--->8------
If changes based on implementation experience and user feedback are made
to Standards track PEPs while in the Accepted or Provisional State,
those changes should be noted in the PEP, such that the PEP accurately
describes the state of the implementation at the point where it is
marked Final.
---->8--------
I don't think that PEP describes the state of art in the decimal module.

> Possibly the decimal documentation could be updated, though.

The current behaviour is documented.  Do you mean we should document
disagreement with PEP as well?

Regarding mail thread: I don't think that following the PEP will
slow down string conversion.  Also, probably we want that strings
that supported by float() and Decimal() were interchangeable.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue44267>
_______________________________________