django1/django/core/management
Przemysław Suliga af5ec222cc Used time.monotonic() instead of time.time() where applicable.
time.monotonic() available from Python 3.3:

- Nicely communicates a narrow intent of "get a local system monotonic
  clock time" instead of possible "get a not necessarily accurate Unix
  time stamp because it needs to be communicated to outside of this
  process/machine" when time.time() is used.
  
- Its result isn't affected by the system clock updates.

There are two classes of time.time() uses changed to time.monotonic()
by this change:

- measuring time taken to run some code.

- setting and checking a "close_at" threshold for for persistent db
  connections (django/db/backends/base/base.py).
2019-05-08 18:34:22 +02:00
..
commands Used time.monotonic() instead of time.time() where applicable. 2019-05-08 18:34:22 +02:00
__init__.py Fixed #30159 -- Removed unneeded use of OrderedDict. 2019-02-06 13:48:39 -05:00
base.py Fixed #30418 -- Added --skip-checks management command option. 2019-04-30 10:48:30 +02:00
color.py Fixed #29560 -- Added --force-color management command option. 2018-09-11 11:15:42 -04:00
sql.py Removed unnecessary assignments in various code. 2019-04-24 13:09:29 +02:00
templates.py Fixed #30393 -- Added validation of startapp's directory option. 2019-04-25 08:52:48 +02:00
utils.py Refs #29973 -- Extracted helper functions from makemessages. 2019-01-28 18:23:41 -05:00