Message95263
| Author | mark.dickinson |
|---|---|
| Recipients | facundobatista, jdunck, lorg, mark.dickinson, rhettinger |
| Date | 2009-11-14.22:37:13 |
| SpamBayes Score | 8.192118e-08 |
| Marked as misclassified | No |
| Message-id | <1258238234.77.0.876707355875.issue2531@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Just closed issue 7323 as a duplicate of this one. I think this issue is worth reopening: with the backport of the py3k correctly rounded string <-> float conversions, there might now be a reasonable way to rewrite Decimal.__hash__ so that it's consistent with float.__hash__. Then we can make Decimal-to-float comparisons behave correctly and clear up this mess. I'd still be uncomfortable with allowing Decimal-to-float comparisons in 2.x but not in 3.x. Maybe they could be permitted in 3.x too? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2009-11-14 22:37:15 | mark.dickinson | set | recipients: + mark.dickinson, rhettinger, facundobatista, jdunck, lorg |
| 2009-11-14 22:37:14 | mark.dickinson | set | messageid: <1258238234.77.0.876707355875.issue2531@psf.upfronthosting.co.za> |
| 2009-11-14 22:37:13 | mark.dickinson | link | issue2531 messages |
| 2009-11-14 22:37:13 | mark.dickinson | create | |