Message 155139 - 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, pitrou, tasslehoff, vstinner
Date	2012-03-08.00:38:56
SpamBayes Score	0.00017754975
Marked as misclassified	No
Message-id	<4F57FFA3.9080601@gmail.com>
In-reply-to	<1331160026.94.0.871481453327.issue14222@psf.upfronthosting.co.za>

Content
> Well, in 3.3 we could use clock_gettime(CLOCK_MONOTONIC) where available. It's better to use time.monotonic(). > That said, this is not specific to Queue.get() and will probably happen with many similar functions taking a timeout parameter. Yep, it may be used for lock.acquire(timeout=timeout) for example. It would help to have a portable monotonic clock API in C.

> Well, in 3.3 we could use clock_gettime(CLOCK_MONOTONIC) where available.

It's better to use time.monotonic().

> That said, this is not specific to Queue.get() and will probably happen with many similar functions taking a timeout parameter.

Yep, it may be used for lock.acquire(timeout=timeout) for example. It 
would help to have a portable monotonic clock API in C.

History
Date	User	Action	Args
2012-03-08 00:38:57	vstinner	set	recipients: + vstinner, pitrou, neologix, tasslehoff
2012-03-08 00:38:57	vstinner	link	issue14222 messages
2012-03-08 00:38:56	vstinner	create