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 belopolsky
Recipients belopolsky, mark.dickinson
Date 2010-06-25.14:09:37
SpamBayes Score 0.00038623693
Marked as misclassified No
Message-id <[email protected]>
In-reply-to
Content
Mark,

I am reassigning this to you for commit review.  I am changing the title to reflect the visible part of the change.  The datetime module gains direct access to system gettimeofday at the C level while time module grows time.gettimeofday() Python method.

I am not sure I made the best choice defining struct timeval on systems without gettimeofday.  Maybe it is better to do

typedef struct timeval _PyTime_timeval;

on systems with  gettimeofday and equivalent explicit definition on systems without.

The cast selection logic for time_t is a bit of a hack as well, but this is the best I could come up with without resorting to configure tests.  Unless this breaks on a known platform, I would rather commit this as is and have a separate project to clean up cross-platform time handling later.

This patch builds on refactoring started in issue9012.
History
Date User Action Args
2010-06-25 14:09:39belopolskysetrecipients: + belopolsky, mark.dickinson
2010-06-25 14:09:39belopolskysetmessageid: <[email protected]>
2010-06-25 14:09:37belopolskylinkissue9079 messages
2010-06-25 14:09:37belopolskycreate