Message323959
| Author | enedil |
|---|---|
| Recipients | belopolsky, enedil, lemburg, mark.dickinson, vstinner |
| Date | 2018-08-23.16:19:02 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1535041142.33.0.56676864532.issue34423@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Although you're right - this issue is specific to pytime.c, when _Py_InIntegralTypeRange() is used with a double, it is actually true that _Py_InIntegralTypeRange() is used with double, in pytime.c only (as a quick recursive grep discovers). Perhaps the macro should be renamed not to cause confusion (include note about floating point, or define it as a function). I don't have good idea on how this issue could be resolved otherwise. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-08-23 16:19:02 | enedil | set | recipients: + enedil, lemburg, mark.dickinson, belopolsky, vstinner |
| 2018-08-23 16:19:02 | enedil | set | messageid: <1535041142.33.0.56676864532.issue34423@psf.upfronthosting.co.za> |
| 2018-08-23 16:19:02 | enedil | link | issue34423 messages |
| 2018-08-23 16:19:02 | enedil | create | |