Message237407
There's a difference in behaviour between the ``fromutc`` method on a tzinfo between Python 2 and Python 3, though only under the specific case of Summer Time in regions whose usual offset is 0.
From what I can tell, it's the Python 3 one which is wrong, based on it no longer matching the sample implementation provided in the docs and on it appearing to report the wrong times for ``datetime.now(tz)`` when on a machine configured for BST during June 2015.
Similar results can also be achieved using a manually constructed ``datetime`` for dates during summer 2014.
I've put the python script (and sample outputs) I used to investigate in a gist at https://gist.github.com/PeterJCLaw/d8bcc168d68acf066811#file-time_issues-py. The outputs there are for pythons 2.7.9 and 3.4.0. |
|
Date |
User |
Action |
Args |
2015-03-07 00:43:03 | peterjclaw | set | recipients:
+ peterjclaw |
2015-03-07 00:43:03 | peterjclaw | set | messageid: <1425688983.27.0.949503850992.issue23600@psf.upfronthosting.co.za> |
2015-03-07 00:43:03 | peterjclaw | link | issue23600 messages |
2015-03-07 00:43:02 | peterjclaw | create | |
|