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 mark.dickinson
Recipients facundobatista, mark.dickinson, rhettinger, skrah
Date 2010-05-22.11:29:39
SpamBayes Score 0.01863544
Marked as misclassified No
Message-id <1274527781.87.0.664952501186.issue8786@psf.upfronthosting.co.za>
In-reply-to
Content
It's Table 3.6 ("Decimal interchange format parameters") in the final version of IEEE 754;  I'm not sure what that corresponds to in the various drafts.  It has column headings: "decimal32", "decimal64", "decimal128" and "decimal{k} (k >= 32)".

Parameters for decimal{k}:  k must be a multiple of 32.  precision is   9*k/32-2.  emax is 3*2**(k/16+3).  I think these formulas all work for the specific cases k in {32, 64, 128} too, so it should be easy to check that they make sense.

They give an example below the table, too:

"For example, decimal256 would have p = 70 and emax = 1572864."
History
Date User Action Args
2010-05-22 11:29:41mark.dickinsonsetrecipients: + mark.dickinson, rhettinger, facundobatista, skrah
2010-05-22 11:29:41mark.dickinsonsetmessageid: <1274527781.87.0.664952501186.issue8786@psf.upfronthosting.co.za>
2010-05-22 11:29:40mark.dickinsonlinkissue8786 messages
2010-05-22 11:29:39mark.dickinsoncreate