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 pitrou
Recipients pitrou, rnk
Date 2011-03-14.17:31:32
SpamBayes Score 1.050271e-13
Marked as misclassified No
Message-id <1300123892.84.0.0445385241671.issue11504@psf.upfronthosting.co.za>
In-reply-to
Content
> It seems reasonable to me that the interpreter should be able to
> initialize and write to stdout in less than half a second

Well, we have some very slow buildbots and others which seem quite loaded too.
(this one should be very fast but perhaps there's some other stuff going on in the background)

In my experience such a low timeout value may be enough for light in-process stuff such as lock.acquire() or select(), but if you spawn a whole new process you should let the system breathe a bit more. I know this also unfortunately increases the test runtime, but try to bump it up to at least 1.5 seconds.
History
Date User Action Args
2011-03-14 17:31:32pitrousetrecipients: + pitrou, rnk
2011-03-14 17:31:32pitrousetmessageid: <1300123892.84.0.0445385241671.issue11504@psf.upfronthosting.co.za>
2011-03-14 17:31:32pitroulinkissue11504 messages
2011-03-14 17:31:32pitroucreate