Message231375
| Author |
ncoghlan |
| Recipients |
Jure.Erznožnik, ncoghlan, skrah |
| Date |
2014年11月19日.12:09:57 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1416398998.19.0.758389637318.issue22900@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I would expect this to be a difference between the original pure Python implementation and the current C accelerated implementation.
The constraint is in alignment with the General Decimal Arithmetic Specification that the decimal module aims to implement, which requires that Emin and Emax define a balanced range about zero. (That is, Emin = -Emax +/- 1)
The fact the pure Python implementation didn't enforce that constraint was an implementation detail - other implementations (including the cdecimal module, which was incorporated into the standard library to provide CPython's C accelerated version in Python 3.3) are free to enforce it. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2014年11月19日 12:09:58 | ncoghlan | set | recipients:
+ ncoghlan, skrah, Jure.Erznožnik |
| 2014年11月19日 12:09:58 | ncoghlan | set | messageid: <1416398998.19.0.758389637318.issue22900@psf.upfronthosting.co.za> |
| 2014年11月19日 12:09:58 | ncoghlan | link | issue22900 messages |
| 2014年11月19日 12:09:57 | ncoghlan | create |
|