Message251675
| Author |
tim.peters |
| Recipients |
alynn, belopolsky, peterjclaw, tim.peters |
| Date |
2015-09-27.03:04:07 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1443323048.57.0.677714200193.issue23600@psf.upfronthosting.co.za> |
| In-reply-to |
|
| Content |
I expect Peter is correct: the C fromutc() doesn't match the logic of the Python fromutc(), and there are no comments explaining why the C version changed the logic.
The last 4 lines of his `time_issues.py` show the difference. The simplified UKSummerTime tzinfo always says the total UTC offset and the DST offset are +1:00:00. The Python .fromutc() adds that hour to the datetime passed in, but the C .fromutc() does not. That's because they implement different functions, not because Peter is using .fromutc() ;-) |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2015-09-27 03:04:08 | tim.peters | set | recipients:
+ tim.peters, belopolsky, alynn, peterjclaw |
| 2015-09-27 03:04:08 | tim.peters | set | messageid: <1443323048.57.0.677714200193.issue23600@psf.upfronthosting.co.za> |
| 2015-09-27 03:04:08 | tim.peters | link | issue23600 messages |
| 2015-09-27 03:04:07 | tim.peters | create | |
|