Message 200834 - Python tracker

➜

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	neologix, vstinner
Date	2013-10-21.20:01:15
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1382385675.07.0.888544622289.issue19339@psf.upfronthosting.co.za>
In-reply-to

Content
While reading the patch attached to #19170, I saw that telnetlib uses time.time() to compute a timeout. This is wrong: the system clock may jump forward or backward (ex: summer/winter time, NTP adjust, manual clock change by the administrator, etc.). time.monotonic() should be used instead. I will work on a patch when #19170 will be fixed (just to avoid conflicts).

While reading the patch attached to #19170, I saw that telnetlib uses time.time() to compute a timeout. This is wrong: the system clock may jump forward or backward (ex: summer/winter time, NTP adjust, manual clock change by the administrator, etc.).

time.monotonic() should be used instead. I will work on a patch when #19170 will be fixed (just to avoid conflicts).

History
Date	User	Action	Args
2013-10-21 20:01:15	vstinner	set	recipients: + vstinner, neologix
2013-10-21 20:01:15	vstinner	set	messageid: <1382385675.07.0.888544622289.issue19339@psf.upfronthosting.co.za>
2013-10-21 20:01:15	vstinner	link	issue19339 messages
2013-10-21 20:01:15	vstinner	create