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, ocean-city |
| Date | 2007年09月24日.16:16:22 |
| SpamBayes Score | 0.00784806 |
| Marked as misclassified | No |
| Message-id | <1190650583.14.0.198320352221.issue1182@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I should have said that the bug I mentioned above is just one of a number of bugs (mostly in division, addition and square root) that have been corrected in the trunk. Some of these fixes should probably be backported. But the decimal module has also had significant new functionality added since Python 2.5, which is going to make sorting out which pieces to backport tricky. Actually, I guess it's possible to argue that the entire new decimal.py module should be backported for inclusion in Python 2.5.2: the new functionality was added to comply with the IBM Decimal Arithmetic specification, and the comments in the decimal module explicitly say that non-compliance with an update specification should be regarded as a bug. So almost all the changes are bugfixes, in some sense... Facundo, what do you think? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2007年09月24日 16:16:23 | mark.dickinson | set | spambayes_score: 0.00784806 -> 0.00784806 recipients: + mark.dickinson, facundobatista, ocean-city |
| 2007年09月24日 16:16:23 | mark.dickinson | set | spambayes_score: 0.00784806 -> 0.00784806 messageid: <1190650583.14.0.198320352221.issue1182@psf.upfronthosting.co.za> |
| 2007年09月24日 16:16:23 | mark.dickinson | link | issue1182 messages |
| 2007年09月24日 16:16:22 | mark.dickinson | create | |