Message127496
| Author | belopolsky |
|---|---|
| Recipients | belopolsky, benjamin.peterson, georg.brandl, lavajoe |
| Date | 2011-01-29.23:07:11 |
| SpamBayes Score | 3.2236626e-06 |
| Marked as misclassified | No |
| Message-id | <AANLkTi=TYDRA1P5KU2nb+g8UYjpkJu6VDCcBKN5s346i@mail.gmail.com> |
| In-reply-to | <1296341279.99.0.372488457466.issue10939@psf.upfronthosting.co.za> |
| Content | |
|---|---|
On Sat, Jan 29, 2011 at 5:48 PM, Joe Peterson <report@bugs.python.org> wrote: .. > Note that this also exposes another problem with Time2Internaldate(), since it uses > time.timezone/time.altzone, which are only valid for the current rules, not old rules as in the London case > near the epoch. This is a known issue. Hopefully this example will raise more interest for issue 9527. See also issue 1647654 which suggests a python-only work-around. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-01-29 23:07:13 | belopolsky | set | recipients: + belopolsky, georg.brandl, benjamin.peterson, lavajoe |
| 2011-01-29 23:07:11 | belopolsky | link | issue10939 messages |
| 2011-01-29 23:07:11 | belopolsky | create | |