Message150335
| Author | tim.golden |
|---|---|
| Recipients | Ramchandra Apte, belopolsky, flox, patrick.vrijlandt, tim.golden, vstinner |
| Date | 2011-12-29.16:59:28 |
| SpamBayes Score | 0.011724751 |
| Marked as misclassified | No |
| Message-id | <1325177969.25.0.306968728989.issue13674@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
This is happening on Windows x86 against the current tip. The MS C runtime can handle older dates; it's just that we're taking 1900 off the year at some point. (At least, I think that's what's happening). FWIW you only need time.strftime to reproduce the error:
import time
time.strftime("%y", (1899, 1, 1, 0, 0, 0, 0, 0, 0))
If no-one gets there first I'll dig into the timemodule strftime wrapper. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-12-29 16:59:29 | tim.golden | set | recipients: + tim.golden, belopolsky, vstinner, flox, patrick.vrijlandt, Ramchandra Apte |
| 2011-12-29 16:59:29 | tim.golden | set | messageid: <1325177969.25.0.306968728989.issue13674@psf.upfronthosting.co.za> |
| 2011-12-29 16:59:28 | tim.golden | link | issue13674 messages |
| 2011-12-29 16:59:28 | tim.golden | create | |