Message65112
| Author | belopolsky |
|---|---|
| Recipients | belopolsky, datacompboy, georg.brandl |
| Date | 2008-04-07.20:04:34 |
| SpamBayes Score | 0.021758342 |
| Marked as misclassified | No |
| Message-id | <d38f5330804071304p147049f8qf5d9dc8b22458589@mail.gmail.com> |
| In-reply-to | <1207597346.71.0.482616903647.issue2568@psf.upfronthosting.co.za> |
| Content | |
|---|---|
On Mon, Apr 7, 2008 at 3:42 PM, Anton Fedorov <report@bugs.python.org> wrote: > There no leap second in 2000th. I was just too lazy too look up the leap second year, but datetime module knows nothing about leap seconds, so I did not expect different behavior for years 1995 and 2000. > But correct time request fails: > >>> datetime.strptime('19951231T235960', '%Y%m%dT%H%M%S') ditto |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008-04-07 20:04:36 | belopolsky | set | spambayes_score: 0.0217583 -> 0.021758342 recipients: + belopolsky, georg.brandl, datacompboy |
| 2008-04-07 20:04:35 | belopolsky | link | issue2568 messages |
| 2008-04-07 20:04:34 | belopolsky | create | |