summaryrefslogtreecommitdiffstats
path: root/Python/pytime.c
Commit message (Collapse)AuthorAgeFilesLines
* Merge 3.5 (pytime)Victor Stinner2015-11-101-3/+3
|\
| * pytime.c: rename pygettimeofday_new() to pygettimeofday()Victor Stinner2015-11-101-3/+3
| | | | | | | | I forgot to rename it in my previous refactoring of pytime.c.
| * Issue #25155: Fix _PyTime_Divide() roundingVictor Stinner2015-09-181-3/+8
| | | | | | | | | | _PyTime_Divide() rounding was wrong: copy code from Python default which has now much better unit tests.
| * Issue #25155: Add _PyTime_AsTimevalTime_t() functionVictor Stinner2015-09-181-38/+61
| | | | | | | | | | | | | | | | | | | | | | | | | | | | On Windows, the tv_sec field of the timeval structure has the type C long, whereas it has the type C time_t on all other platforms. A C long has a size of 32 bits (signed inter, 1 bit for the sign, 31 bits for the value) which is not enough to store an Epoch timestamp after the year 2038. Add the _PyTime_AsTimevalTime_t() function written for datetime.datetime.now(): convert a _PyTime_t timestamp to a (secs, us) tuple where secs type is time_t. It allows to support dates after the year 2038 on Windows. Enhance also _PyTime_AsTimeval_impl() to detect overflow on the number of seconds when rounding the number of microseconds.
* | Issue #25558: Use compile-time asserts.Serhiy Storchaka2015-11-071-13/+12
| |
* | Fix _PyTime_AsTimevalStruct_impl() on OpenBSDVictor Stinner2015-10-011-2/+3
| | | | | | | | | | | | On the x86 OpenBSD 5.8 buildbot, the integer overflow check is ignored. Copy the tv_sec variable into a Py_time_t variable instead of "simply" casting it to Py_time_t, to fix the integer overflow check.
* | Backout change 28d3bcb1bad6: "Try to fix _PyTime_AsTimevalStruct_impl() onVictor Stinner2015-09-301-3/+2
| | | | | | | | | | OpenBSD", I'm not sure that the change was really needed. I read the test result of an old build because the OpenBSD was 100 builds late.
* | Try to fix _PyTime_AsTimevalStruct_impl() on OpenBSDVictor Stinner2015-09-291-2/+3
| | | | | | | | It looks like the check for integer overflow doesn't work on x86 OpenBSD 5.8.
* | Issue #25155: Add _PyTime_AsTimevalTime_t() functionVictor Stinner2015-09-181-19/+60
| | | | | | | | | | | | | | | | | | | | | | | | | | | | On Windows, the tv_sec field of the timeval structure has the type C long, whereas it has the type C time_t on all other platforms. A C long has a size of 32 bits (signed inter, 1 bit for the sign, 31 bits for the value) which is not enough to store an Epoch timestamp after the year 2038. Add the _PyTime_AsTimevalTime_t() function written for datetime.datetime.now(): convert a _PyTime_t timestamp to a (secs, us) tuple where secs type is time_t. It allows to support dates after the year 2038 on Windows. Enhance also _PyTime_AsTimeval_impl() to detect overflow on the number of seconds when rounding the number of microseconds.
* | pytime: oops, fix typos on WindowsVictor Stinner2015-09-101-2/+2
| |
* | pytime: add _PyTime_check_mul_overflow() macro to avoid undefined behaviourVictor Stinner2015-09-101-11/+24
| | | | | | | | | | | | | | | | | | | | | | Overflow test in test_FromSecondsObject() fails on FreeBSD 10.0 buildbot which uses clang. clang implements more aggressive optimization which gives different result than GCC on undefined behaviours. Check if a multiplication will overflow, instead of checking if a multiplicatin had overflowed, to avoid undefined behaviour. Add also debug information if the test on overflow fails.
* | New try to fix test_time.test_AsSecondsDouble() on x86 buildbots.Victor Stinner2015-09-101-2/+7
| | | | | | | | Use volatile keyword in _PyTime_AsSecondsDouble()
* | Try to fix test_time.test_AsSecondsDouble() on "x86 Gentoo Non-Debug with X ↵Victor Stinner2015-09-101-3/+8
| | | | | | | | | | | | 3.x" buildbot Use volatile keyword in _PyTime_Round()
* | Fix test_time on WindowsVictor Stinner2015-09-101-20/+8
| | | | | | | | | | | | | | * Filter values which would overflow on conversion to the C long type (for timeval.tv_sec). * Adjust also the message of OverflowError on PyTime conversions * test_time: add debug information if a timestamp conversion fails
* | test_time: rewrite PyTime API rounding testsVictor Stinner2015-09-091-6/+10
| | | | | | | | | | | | | | | | | | | | Drop all hardcoded tests. Instead, reimplement each function in Python, usually using decimal.Decimal for the rounding mode. Add much more values to the dataset. Test various timestamp units from picroseconds to seconds, in integer and float. Enhance also _PyTime_AsSecondsDouble().
* | pytime: add _PyTime_Round() helper to factorize codeVictor Stinner2015-09-091-25/+20
| |
* | Make _PyTime_RoundHalfEven() private againVictor Stinner2015-09-091-1/+3
| |
* | Issue #23517: fromtimestamp() and utcfromtimestamp() methods ofVictor Stinner2015-09-081-42/+29
| | | | | | | | | | | | | | | | | | | | | | | | datetime.datetime now round microseconds to nearest with ties going to nearest even integer (ROUND_HALF_EVEN), as round(float), instead of rounding towards -Infinity (ROUND_FLOOR). pytime API: replace _PyTime_ROUND_HALF_UP with _PyTime_ROUND_HALF_EVEN. Fix also _PyTime_Divide() for negative numbers. _PyTime_AsTimeval_impl() now reuses _PyTime_Divide() instead of reimplementing rounding modes.
* | Issue #23517: Fix implementation of the ROUND_HALF_UP rounding mode inVictor Stinner2015-09-041-4/+4
| | | | | | | | | | datetime.datetime.fromtimestamp() and datetime.datetime.utcfromtimestamp(). microseconds sign should be kept before rounding.
* | Don't abuse volatile keyword in pytime.cVictor Stinner2015-09-031-2/+4
| | | | | | | | | | Only use it on the most important number. This change fixes also a compiler warning on modf().
* | Enhance _PyTime_AsTimespec()Victor Stinner2015-09-031-3/+3
| | | | | | | | | | Ensure that the tv_nsec field is set, even if the function fails with an overflow.
* | Merge 3.5 (monotonic)Victor Stinner2015-09-021-13/+3
|\ \ | |/
| * oops, rename pymonotonic_new() to pymonotonic()Victor Stinner2015-09-021-3/+3
| | | | | | | | | | I was not supposed to commit the function with the name pymonotonic_new(). I forgot to rename it.
| * Issue #24707: Remove assertion in monotonic clockVictor Stinner2015-09-021-10/+0
| | | | | | | | | | | | | | | | | | | | Don't check anymore at runtime that the monotonic clock doesn't go backward. Yes, it happens. It occurs sometimes each month on a Debian buildbot slave running in a VM. The problem is that Python cannot do anything useful if a monotonic clock goes backward. It was decided in the PEP 418 to not fix the system, but only expose the clock provided by the OS.
* | Issue #23517: datetime.timedelta constructor now rounds microseconds to nearestVictor Stinner2015-09-021-2/+1
| | | | | | | | | | | | with ties going away from zero (ROUND_HALF_UP), as Python 2 and Python older than 3.3, instead of rounding to nearest with ties going to nearest even integer (ROUND_HALF_EVEN).
* | Issue #23517: Try to fix test_time on "x86 Ubuntu Shared 3.x" buildbotVictor Stinner2015-09-021-7/+10
| |
* | Issue #23517: Fix _PyTime_ObjectToDenominator()Victor Stinner2015-09-021-18/+17
| | | | | | | | | | * initialize numerator on overflow error ensure that numerator is smaller than * denominator.
* | Issue #23517: Add "half up" rounding mode to the _PyTime APIVictor Stinner2015-09-011-10/+54
| |
* | Move assertion inside _PyTime_ObjectToTimeval()Victor Stinner2015-09-011-6/+14
| | | | | | | | | | Change also _PyTime_FromSeconds() assertion to ensure that the _PyTime_t type is used.
* | Refactor pytime.cVictor Stinner2015-09-011-48/+65
|/ | | | Move code to convert double timestamp to subfunctions.
* Issue #22117: Add a new _PyTime_FromSeconds() functionVictor Stinner2015-04-031-0/+17
| | | | | Fix also _Py_InitializeEx_Private(): initialize time before initializing import, import_init() uses the _PyTime API (for thread locks).
* Issue #22117, issue #23485: Fix _PyTime_AsMilliseconds() andVictor Stinner2015-04-011-13/+13
| | | | | | _PyTime_AsMicroseconds() rounding. Add also unit tests.
* Issue #23485: Add _PyTime_FromMillisecondsObject() functionVictor Stinner2015-03-301-5/+18
|
* Issue #22117: Try to fix rounding in conversion from Python double to _PyTime_tVictor Stinner2015-03-301-1/+2
| | | | using the C volatile keyword.
* Issue #22117: Remove _PyTime_ROUND_DOWN and _PyTime_ROUND_UP rounding methodsVictor Stinner2015-03-301-15/+5
| | | | Use _PyTime_ROUND_FLOOR and _PyTime_ROUND_CEILING instead.
* Issue #22117: Add _PyTime_ROUND_CEILING rounding method for timestampsVictor Stinner2015-03-301-0/+2
| | | | Add also more tests for ROUNd_FLOOR.
* Issue #22117: Add assertions to _PyTime_AsTimeval() and _PyTime_AsTimespec() toVictor Stinner2015-03-301-0/+4
| | | | check that microseconds and nanoseconds fits into the specified range.
* Issue #22117: Fix usage of _PyTime_AsTimeval()Victor Stinner2015-03-301-2/+17
| | | | | Add _PyTime_AsTimeval_noraise() function. Call it when it's not possible (or not useful) to raise a Python exception on overflow.
* Issue #22117: Fix rounding and implement _PyTime_ROUND_FLOOR in:Victor Stinner2015-03-291-24/+20
| | | | | | - _PyTime_ObjectToTime_t() - _PyTime_ObjectToTimespec() - _PyTime_ObjectToTimeval()
* Issue #22117: Cleanup pytime.c/.hVictor Stinner2015-03-291-7/+5
|
* Issue #22117: Use the _PyTime_t API in _datetime.datetime() constructorVictor Stinner2015-03-291-105/+14
| | | | | * Remove _PyTime_gettimeofday() * Add _PyTime_GetSystemClock()
* Issue #22117: Fix _PyTime_GetMonotonicClock() andVictor Stinner2015-03-281-12/+20
| | | | | _PyTime_GetSystemClockWithInfo() to not raise an exception and return 0 on error (it should never occur)
* Issue #22117: Add the new _PyTime_ROUND_FLOOR rounding method for the datetimeVictor Stinner2015-03-281-3/+12
| | | | | module. time.clock_settime() now uses this rounding method instead of _PyTime_ROUND_DOWN to handle correctly dates before 1970.
* Issue #22117: Use the _PyTime_t API for time.clock_settime()Victor Stinner2015-03-281-17/+0
| | | | Remove also the now unused _PyTime_AddDouble() function.
* Issue #22117: Use the new _PyTime_t API in the select moduleVictor Stinner2015-03-281-1/+1
|
* Issue #22117: The thread module uses the new _PyTime_t timestamp APIVictor Stinner2015-03-281-126/+6
| | | | | | | | | Add also a new _PyTime_AsMicroseconds() function. threading.TIMEOUT_MAX is now be smaller: only 292 years instead of 292,271 years on 64-bit system for example. Sorry, your threads will hang a *little bit* shorter. Call me if you want to ensure that your locks wait longer, I can share some tricks with you.
* Issue #22117: Write unit tests for _PyTime_AsTimeval()Victor Stinner2015-03-281-13/+27
| | | | | | | * _PyTime_AsTimeval() now ensures that tv_usec is always positive * _PyTime_AsTimespec() now ensures that tv_nsec is always positive * _PyTime_AsTimeval() now returns an integer on overflow instead of raising an exception
* Issue #22117: The signal modules uses the new _PyTime_t APIVictor Stinner2015-03-271-0/+21
| | | | | * Add _PyTime_AsTimespec() * Add unit tests for _PyTime_AsTimespec()
* Issue #22117: time.time() now uses the new _PyTime_t APIVictor Stinner2015-03-271-9/+120
| | | | * Add _PyTime_GetSystemClockWithInfo()
* Issue #22117: time.monotonic() now uses the new _PyTime_t APIVictor Stinner2015-03-271-0/+26
| | | | | | * Add _PyTime_FromNanoseconds() * Add _PyTime_AsSecondsDouble() * Add unit tests for _PyTime_AsSecondsDouble()
generated by cgit v0.12 at 2024-09-23 17:14:29 (GMT)