This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Sergey.Kirpichev
Recipients Sergey.Kirpichev, facundobatista, mark.dickinson, rhettinger
Date 2021-05-30.08:52:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <YLNSMBrZsgkTqe3+@note>
In-reply-to <1622363560.76.0.91696102304.issue44267@roundup.psfhosted.org>
Content
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.
History
Date User Action Args
2021-05-30 08:52:05Sergey.Kirpichevsetrecipients: + Sergey.Kirpichev, rhettinger, facundobatista, mark.dickinson
2021-05-30 08:52:05Sergey.Kirpichevlinkissue44267 messages
2021-05-30 08:52:05Sergey.Kirpichevcreate