Datetime and Time packages do not have the same behavior when being frozen about freezegun

[bblommers]

Hi @folkvir! I created a standalone test case in #537 - if I'm understanding the problem correctly, that demonstrates the fact that there is indeed a bug here.

I think the appropriate fix is to extend all FakeDatetime methods to use should_use_real_time, but I don't have a lot of time to look into this - so PR's are welcome.

[folkvir]

I'll try to look into it and create a pull request as soon as possible but I don't have a lot of time to spend outside my family and job. So if someone has more free time then go!

[folkvir]

@bblommers Ok after investigations I found calling print(_should_use_real_time()) in the beginning of FakeDatetime.now return "False" because the module name returned by: frame.f_globals.get('__name__') is never listed in ignore_lists[-1]. The ignore_list[-1] is ('tests.another_module', 'nose.plugins', 'six.moves', 'django.utils.six.moves', 'google.gax', 'threading', 'multiprocessing', 'queue', 'selenium', '_pytest.terminal.', '_pytest.runner.', 'gi', 'prompt_toolkit') but the module_name(s) are just:

freezegun.api
tests.test_configure
_pytest.python
pluggy._callers
pluggy._manager

Increasing the call_stack_inspection_limit does not change anything.
So even if we patch FakeDateTime.now with a usage of _should_use_real_time then we won't get the real_time because the function always return false!

[folkvir]

Update: I think I found the core of the bug; but it may be an artefact of the test setup because we locally import the another_module module. The bug should be reproductible if you comment my changes in freezegun.api.
Changes: master...folkvir:freezegun:bug/ignore-fakedatetime-bug