This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | davidfraser |
|---|---|
| Recipients | benno, davidfraser, loewis, skip.montanaro |
| Date | 2008年05月10日.20:41:45 |
| SpamBayes Score | 0.16198638 |
| Marked as misclassified | No |
| Message-id | <1210452108.67.0.346434534295.issue1777412@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> Which version of Python are you using? I could have sworn we just fixed this problem in CVS a couple weeks ago. This was on the latest Python 2.6 svn... but looking at the py3k branch with viewsvn the code is definitely still there too... The relevant commit seems to be r30224 in 2002: > I give up: unless I write my own strftime by hand, datetime just can't be trusted with years before 1900, so now we raise ValueError if a date or datetime or datetimetz .strftime() method is called with a year before 1900. Of course I'm not dealing with any of this in the attached patch, but then I don't have the information on which platforms have the problem... but according to the above writing strftime by hand would be the only solution... |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年05月10日 20:41:49 | davidfraser | set | spambayes_score: 0.161986 -> 0.16198638 recipients: + davidfraser, loewis, skip.montanaro, benno |
| 2008年05月10日 20:41:48 | davidfraser | set | spambayes_score: 0.161986 -> 0.161986 messageid: <1210452108.67.0.346434534295.issue1777412@psf.upfronthosting.co.za> |
| 2008年05月10日 20:41:48 | davidfraser | link | issue1777412 messages |
| 2008年05月10日 20:41:46 | davidfraser | create | |