Testing asyncio code made harder due to freezing time.monotonic()

Hi,

Version 1.1.0 makes it harder to test asyncio-based code relying on asyncio.sleep(), asyncio.wait_for(), … where what we only want to test is datetime related. In such cases, without any auto or manual ticking all time based awaits simply freeze because : The event loop has its own internal clock for computing timeouts. Which clock is used depends on the (platform-specific) event loop implementation; ideally it is a monotonic clock. This will generally be a different clock than time.time(). (See https://docs.python.org/3.6/library/asyncio-eventloop.html#asyncio-delayed-calls).

Would it be possible to make time.monotonic() freezing optional?

[romainletendart]

That indeed did the trick for me:

with freezegun.freeze_time(dt, ignore=['asyncio']):
    # asyncio time-based code

Thank you very much!

[boxed]

That good but I don’t think this means we should close the ticket? The question is if freezegun needs to have this in the ignore list or not. I don’t think it’s obvious.

Could you maybe show a minimal program that shows this issue? I think this would help me understand if freezegun needs to be changed.