Message167348
| Author | pitrou |
|---|---|
| Recipients | mark.dickinson, pitrou, skrah, steven.daprano |
| Date | 2012-08-03.19:49:30 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1344023218.3377.10.camel@localhost.localdomain> |
| In-reply-to | <1344023256.24.0.235062758077.issue15544@psf.upfronthosting.co.za> |
| Content | |
|---|---|
> > Why not add a is_nan() method to float numbers instead? > > Do you mean replacing math.isnan(x) by x.is_nan() to avoid the issue > altogether? I'm not sure that's possible given that math just wraps > the C library. Yup. By calling x.is_nan() you would by construction get an implementation that's correct for x's type. If x is a float, it would obviously re-use math.isnan() (or have a similar implementation). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012-08-03 19:49:31 | pitrou | set | recipients: + pitrou, mark.dickinson, steven.daprano, skrah |
| 2012-08-03 19:49:31 | pitrou | link | issue15544 messages |
| 2012-08-03 19:49:30 | pitrou | create | |