Different behaviour between Python 2 and 3 about freezegun

[spulec]

After digging into this a bit, I don't think the issue is with freezegun. Try running the following on python2 and python3 and notice the different results.

import datetime
from dateutil.tz import *
tz = gettz('Europe/London')
print(tz.fromutc(datetime.datetime(2014, 4, 26, 12, 1).replace(tzinfo=tz)))

Also notice that if we change the datetime to datetime.datetime(2014, 1, 26, 12, 1), then everything works.

I don't have more time to dig into this right now. If you keep digging, let me know what you find.

[PeterJCLaw]

Thanks. It turns out that it only expresses an issue when the timezone has an ordinary offset of 0 (ie UTC), but does have a summer-time component.
I've raised an issue against Python 3.4 here: http://bugs.python.org/issue23600.

[spulec]

Hmmm, very interesting.

I'm going to close this for now. Feel free to reopen if I can be of assistance or you think there is an easy workaround for freezegun to use, although I am a bit worried it could create more confusion. Also, feel free to comment here if any progress is made on your Python ticket.

[PeterJCLaw]

Update: It's been fixed in the python 3.4, 3.5 and 3.6 streams.

[spulec]

Awesome, thanks!