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
Date 2008-07-25.22:16:12
SpamBayes Score 0.004444105
Marked as misclassified No
Message-id <1217024173.73.0.509387399597.issue3449@psf.upfronthosting.co.za>
In-reply-to
Content
The IBM General Decimal Arithmetic Specification, on which the decimal 
module is based, has recently been updated to version 1.68;  the 
testcases from IBM have also been updated.

The comments in the decimal module clearly state that the decimal module 
should be kept in sync with the IBM specification, and that deviation 
from the spec is considered a bug.  So it seems to me that the decimal 
module should be updated, preferably before 2.6 and 3.0 come out.

As far as I can tell the required changes should be minimal:  max-
magnitude and min-magnitude definitely need changing, and there may be 
other minor changes necessary to make the new tests pass; I haven't 
looked properly yet.  I'll try to get to this in the next few days.
History
Date User Action Args
2008-07-25 22:16:13mark.dickinsonsetspambayes_score: 0.00444411 -> 0.004444105
recipients: + mark.dickinson, rhettinger, facundobatista
2008-07-25 22:16:13mark.dickinsonsetspambayes_score: 0.00444411 -> 0.00444411
messageid: <1217024173.73.0.509387399597.issue3449@psf.upfronthosting.co.za>
2008-07-25 22:16:13mark.dickinsonlinkissue3449 messages
2008-07-25 22:16:12mark.dickinsoncreate