Faked time shouldn't always be the same.

Excerpt from the docs: “[…] all calls to datetime.datetime.now(), datetime.datetime.utcnow(), […] will return the time that has been frozen.”

But this is not the behaviour I expect.

Example code:

from datetime import datetime

def test_something():
    print('now():   ', datetime.now())
    print('utcnow():', datetime.utcnow())

Output without Freezegun (system timezone is “Europe/Berlin”):

now():    2015-03-10 00:46:40.465879
utcnow(): 2015-03-09 23:46:40.466031

Output with Freezegun (method decorated with @freeze_time('2012-03-11 19:21:23')):

now():    2012-03-11 19:21:23
utcnow(): 2012-03-11 19:21:23

However, I expected the output with Freezegun to reflect the offset (one hour, in this case) and, thus, to return two different date/time instances.

[boxed]

@charettes For me the point of freeze_time is that you create a world where time related things are predictable and portable across machines. Leaving the time zone as is will not satisfy this demand.

I’m all for having a nicer way to freeze but still respect the time zone if that’s what you want though. I’d also like a better way to “freeze” and still respect the local time! This is super useful to initialize the monkey patching just once for your entire test suite for example. We do this at work (and we use my fork that is also an active PR) and it has some pretty dramatic performance advantages if you freeze time a lot.

I’d suggest this:

• freeze_time('local', tzinfo='local', tick=True) for respecting time zone, local time and keeping the clock moving
• freeze_time('2001-01-02', tzinfo='local') for respecting local time zone but locking the rest
• freeze_time('2001-01-02') for locking everything

…as for tzinfo vs tzoffset I’m all for it. The only problem I see with it is that if you specify a time zone by name that can mean something different at some later point. tzoffset doesn’t have this problem, but it also doesn’t model DST properly, so I think maybe a third option is needed here? In addition to your suggestion that is.

[sjlehtin]

From this thread we can get some test cases on how it should work, and from the other duplicates as well. I guess no one actually did a full summary of the related issues?

I guess I can give this a shot as I need to work around this right now.