➜

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 rcohen
Recipients brian.curtin, jnoller, kevinwatters, lemburg, nascheme, pitrou, rcohen, schmir
Date 2010-01-26.23:15:03
SpamBayes Score 2.5176215e-07
Marked as misclassified No
Message-id <20100126151155.5cda9e74@neeble>
In-reply-to <1264152753.17.0.656147876949.issue7753@psf.upfronthosting.co.za>
Content 
On Fri, 22 Jan 2010 09:32:36 +0000
Marc-Andre Lemburg <report@bugs.python.org> wrote:

>  * Please add the fallback solutions from the time module in case gettimeofday() is not available. You cannot assume that "all modern POSIX systems" implement that API - it was introduced in POSIX 2001 and Python 2.x still supports OSes that were released prior to that year.

POSIX as a standard tends to follow, not lead. The gettimeofday() call
dates back over 20 years in BSD. time.time() falls back on ftime() and
then time(). ftime() was added to the POSIX spec at the same time as
gettimeofday() and is now deprecated. time() probably doesn't have
enough resolution.

I'd have to be pointed to a specific platform which doesn't support
gettimeofday() but which is supported by python. Otherwise, I'd be
coding blind.

Ross
History
Date User Action Args
2010-01-26 23:15:06rcohensetrecipients: + rcohen, lemburg, nascheme, pitrou, schmir, kevinwatters, jnoller, brian.curtin
2010-01-26 23:15:04rcohenlinkissue7753 messages
2010-01-26 23:15:03rcohencreate