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 kh90909
Recipients docs@python, kh90909, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2019-06-20.04:20:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1561004420.41.0.714810237492.issue37205@roundup.psfhosted.org>
In-reply-to
Content
Hi Terry,

I'm new to this so apologies in advance if this is a silly question...can you explain why you removed 3.5 and 3.6 from the versions list? I have tested that the issue is present in 3.6 and the offending code has been present since time.perf_counter() was introduced in 3.3.

It it because these versions are in maintenance-only status or similar, such that this type of bug fix would not be considered?

Thanks,
Ken
History
Date User Action Args
2019-06-20 04:20:20kh90909setrecipients: + kh90909, paul.moore, vstinner, tim.golden, docs@python, zach.ware, steve.dower
2019-06-20 04:20:20kh90909setmessageid: <1561004420.41.0.714810237492.issue37205@roundup.psfhosted.org>
2019-06-20 04:20:20kh90909linkissue37205 messages
2019-06-20 04:20:20kh90909create