This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | vstinner |
|---|---|
| Recipients | ido k, vstinner |
| Date | 2019年01月15日.17:57:17 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1547575037.6.0.263592553576.issue35747@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
Python 3 uses a monotonic clock to implement timeouts, such clock is not affected by system clock changes *on purpose*. See time.monotonic() and PEP 418: https://docs.python.org/dev/library/time.html#time.monotonic https://www.python.org/dev/peps/pep-0418/ Relying on the system clock can cause severe bugs. I suggest to close this issue as "not a bug". |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019年01月15日 17:57:18 | vstinner | set | recipients: + vstinner, ido k |
| 2019年01月15日 17:57:17 | vstinner | set | messageid: <1547575037.6.0.263592553576.issue35747@roundup.psfhosted.org> |
| 2019年01月15日 17:57:17 | vstinner | link | issue35747 messages |
| 2019年01月15日 17:57:17 | vstinner | create | |