Message129339
| Author |
eli.bendersky |
| Recipients |
docs@python, eli.bendersky, georg.brandl, giampaolo.rodola, ncoghlan, terry.reedy |
| Date |
2011年02月25日.09:30:00 |
| SpamBayes Score |
1.6892653e-06 |
| Marked as misclassified |
No |
| Message-id |
<1298626201.02.0.0537082771643.issue11015@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Georg,
Good catch on the tuples in assertAlmostEqual, thanks! I see three methods of resolution:
1. Since the floats in this case are powers of 1/2, they could be tested for exact equality, or do you figure there are platforms where this is not guaranteed?
2. I can make a local change in the test to assertAlmostEqual on each member of the tuple
3. assertAlmostEqual on tuples can be added to the unittest module
Any ideas?
I can also commit (2) for the time being since it's the least dubious, and leave the resolution on 1 & 3 for later (and/or in separate issues).
Regarding fcmp being not exactly assertAlmostEqual - it was discussed. |
|