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 skrah
Recipients Keith.Brafford, eric.smith, ezio.melotti, facundobatista, mark.dickinson, rhettinger, serge.stroobandt, skrah, tim.peters
Date 2016-01-27.21:01:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1453928493.95.0.922292220878.issue26223@psf.upfronthosting.co.za>
In-reply-to
Content
The spec was the only reasonable choice at the time decimal.py was
written.  Incidentally, it is basically IEEE-754-2008 with arbitrary
precision extensions; this isn't surprising since Mike Cowlishaw was
on the IEEE committee and wrote the spec at the same time.

There are very few decNumber-specific remainders in the spec -- this
may be one of those (though I did not bother to look up if the IEEE
standard specifies formatting at all).
History
Date User Action Args
2016-01-27 21:01:34skrahsetrecipients: + skrah, tim.peters, rhettinger, facundobatista, mark.dickinson, eric.smith, ezio.melotti, Keith.Brafford, serge.stroobandt
2016-01-27 21:01:33skrahsetmessageid: <1453928493.95.0.922292220878.issue26223@psf.upfronthosting.co.za>
2016-01-27 21:01:33skrahlinkissue26223 messages
2016-01-27 21:01:33skrahcreate