I think we should punt on this one.  When the clock changes, it is hard to detect when it happens, how much it changed, what the interactions are with other time dependent routines (logging, etc), and what to do about it.  Much of this is pure guesswork.

It would be different if there we some API in-place for clock changes to notify all of its clients when a change occurs.  But there isn't.  The responsibility for handling clock changes has to lie with the changer, not with all possible clients that call time() or sleep.

Recommend closing as WontFix.