Message 62777 - 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	maltehelmert
Recipients	belopolsky, gvanrossum, maltehelmert, pitrou
Date	2008-02-23.17:21:22
SpamBayes Score	0.012794091
Marked as misclassified	No
Message-id	<1203787284.06.0.853934725202.issue1040026@psf.upfronthosting.co.za>
In-reply-to

Content
Using 1.0 would certainly be more robust. I wasn't sure if a slow-down of "make test" by 1 second just for this one bug would be acceptable. Regarding the fork, when I first encountered this bug, it was in the context of measuring the runtime of child processes, so that's what I tried to reproduce. But looking at the code, the bug should occur just as well with the running process itself. So you're right; one could just busy-wait for a second and then look at times()[0] and times()[1].

Using 1.0 would certainly be more robust. I wasn't sure if a slow-down
of "make test" by 1 second just for this one bug would be acceptable.

Regarding the fork, when I first encountered this bug, it was in the
context of measuring the runtime of child processes, so that's what I
tried to reproduce. But looking at the code, the bug should occur just
as well with the running process itself. So you're right; one could just
busy-wait for a second and then look at times()[0] and times()[1].

History
Date	User	Action	Args
2008-02-23 17:21:24	maltehelmert	set	spambayes_score: 0.0127941 -> 0.012794091 recipients: + maltehelmert, gvanrossum, belopolsky, pitrou
2008-02-23 17:21:24	maltehelmert	set	spambayes_score: 0.0127941 -> 0.0127941 messageid: <1203787284.06.0.853934725202.issue1040026@psf.upfronthosting.co.za>
2008-02-23 17:21:23	maltehelmert	link	issue1040026 messages
2008-02-23 17:21:22	maltehelmert	create