Message270371
| Author | martin.panter |
|---|---|
| Recipients | BreamoreBoy, belopolsky, flox, martin.panter, python-dev, vstinner |
| Date | 2016-07-14.05:41:47 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1468474909.35.0.161582020963.issue13312@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
If you enable GCC’s -ftrapv option, the subtraction overflow triggers an abort. Alexander’s patch works around the problem for asctime(), but the problem still exists in other cases, such as: >>> time.mktime((-2**31 + 1899, *(0,) * 8)) Aborted (core dumped) [Exit 134] Attaching a version of the patch without the conflicting whitespace changes. Why does Python even need to support such extreme time values? It would seem much simpler to raise an exception. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2016-07-14 05:41:49 | martin.panter | set | recipients: + martin.panter, belopolsky, vstinner, flox, BreamoreBoy, python-dev |
| 2016-07-14 05:41:49 | martin.panter | set | messageid: <1468474909.35.0.161582020963.issue13312@psf.upfronthosting.co.za> |
| 2016-07-14 05:41:49 | martin.panter | link | issue13312 messages |
| 2016-07-14 05:41:49 | martin.panter | create | |