Use python 3.3 time.monotonic() instead of time.time()

rsmills36 / pyftpdlib

Automatically exported from code.google.com/p/pyftpdlib

Other

0 stars 0 forks source link

Use python 3.3 time.monotonic() instead of time.time() #247

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

...because it's not affected by system clock updates:
http://docs.python.org/3/library/time.html#time.monotonic
A system clock update can mess up a scheduled function 
(self.ioloop.call_later(timeout, fun)).
Older Python versions will keep using time.time().

Original issue reported on code.google.com by g.rodola on 7 Apr 2013 at 11:46

GoogleCodeExporter commented 9 years ago

Fixed in r1207.

Original comment by g.rodola on 8 Apr 2013 at 1:19

Changed state: FixedInSVN

GoogleCodeExporter commented 9 years ago

Original comment by g.rodola on 9 Apr 2013 at 2:47

Added labels: Milestone-1.1.0
Removed labels: Milestone-1.0.2

GoogleCodeExporter commented 9 years ago

Original comment by g.rodola on 9 Apr 2013 at 4:29

Changed state: Fixed