Message231374
| Author |
Jure.Erznožnik |
| Recipients |
Jure.Erznožnik |
| Date |
2014年11月19日.11:51:38 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1416397899.98.0.98334629396.issue22900@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
At some point since Python 2.7, the EMin, Emax members got more restrictive bounds. Emin cannot go above 0 and Emax cannot go below 0.
I would argue against this logic:
.prec specifies total precision
.Emin and .Emax effectively limit possible locations of decimal point within the given precision. Since they don't specify / enforce EXACT position of the decimal point, what's the point of limiting them?
Without restrictions, setting Emin = Emax = some positive number effectively restricts number of decimal places to exactly that positive number without a need for separate (and expensive) .quantize() calls.
Removing this restriction provides an option to use decimal as true fixed-point arithmetic. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2014年11月19日 11:51:40 | Jure.Erznožnik | set | recipients:
+ Jure.Erznožnik |
| 2014年11月19日 11:51:39 | Jure.Erznožnik | set | messageid: <1416397899.98.0.98334629396.issue22900@psf.upfronthosting.co.za> |
| 2014年11月19日 11:51:39 | Jure.Erznožnik | link | issue22900 messages |
| 2014年11月19日 11:51:38 | Jure.Erznožnik | create |
|