[issue27916] Use time.monotonic instead of time.time where appropriate

[Raymond Hettinger]

Raymond Hettinger added the comment:

Some of these look gratuitous to me, possibly a wholesale search and replace without detailed consideration of each change.  For example, the quick informational timing in random.py does not have any downside for using the regular time.time().  The changes to asyncio and multiprocessing may be warranted.

Davin, would you look at the multiprocessing portion of the patch?

Guido, can you nosy whoever the relevant maintainer is for the asyncio niggling details?

----------
nosy: +davin, gvanrossum, rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue27916>
_______________________________________