ec26f83f2e
Issue #25155 : Fix _PyTime_Divide() rounding
...
_PyTime_Divide() rounding was wrong: copy code from Python default which has
now much better unit tests.
2015-09-18 14:21:14 +02:00
e5b5895b5b
Issue #24917 : time_strftime() buffer over-read.
2015-09-06 19:20:51 -07:00
62b24624dd
Backing out 09b62202d9b7; the tests fail on Linux, and it needs a re-think.
2015-09-06 00:31:02 -07:00
373602fa3f
Issue #24917 : time_strftime() Buffer Over-read. Patch by John Leitch.
2015-09-05 12:16:06 -07:00
7aec764d73
Closes #24244 : Removes invalid test from test_time
2015-06-23 20:48:32 -07:00
13019fdef3
Issue #22117 : Add a new _PyTime_FromSeconds() function
...
Fix also _Py_InitializeEx_Private(): initialize time before initializing
import, import_init() uses the _PyTime API (for thread locks).
2015-04-03 13:10:54 +02:00
62d1c70eff
Issue #22117 , issue #23485 : Fix _PyTime_AsMilliseconds() and
...
_PyTime_AsMicroseconds() rounding.
Add also unit tests.
2015-04-01 17:47:07 +02:00
a695f83f0d
Issue #22117 : Remove _PyTime_ROUND_DOWN and _PyTime_ROUND_UP rounding methods
...
Use _PyTime_ROUND_FLOOR and _PyTime_ROUND_CEILING instead.
2015-03-30 03:57:14 +02:00
bcdd777d3c
Issue #22117 : Add _PyTime_ROUND_CEILING rounding method for timestamps
...
Add also more tests for ROUNd_FLOOR.
2015-03-30 03:52:49 +02:00
f81f0f9c63
Issue #22117 : Fix rounding and implement _PyTime_ROUND_FLOOR in:
...
- _PyTime_ObjectToTime_t()
- _PyTime_ObjectToTimespec()
- _PyTime_ObjectToTimeval()
2015-03-30 00:44:06 +02:00
02937aab13
Issue #22117 : Add the new _PyTime_ROUND_FLOOR rounding method for the datetime
...
module. time.clock_settime() now uses this rounding method instead of
_PyTime_ROUND_DOWN to handle correctly dates before 1970.
2015-03-28 05:02:39 +01:00
95e9cef6f0
Issue #22117 : Write unit tests for _PyTime_AsTimeval()
...
* _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
2015-03-28 01:26:47 +01:00
34dc0f46ae
Issue #22117 : The signal modules uses the new _PyTime_t API
...
* Add _PyTime_AsTimespec()
* Add unit tests for _PyTime_AsTimespec()
2015-03-27 18:19:03 +01:00
4bfb460d88
Issue #22117 : time.monotonic() now uses the new _PyTime_t API
...
* Add _PyTime_FromNanoseconds()
* Add _PyTime_AsSecondsDouble()
* Add unit tests for _PyTime_AsSecondsDouble()
2015-03-27 22:27:24 +01:00
992c43fec9
Issue #22117 : Fix rounding in _PyTime_FromSecondsObject()
...
* Rename _PyTime_FromObject() to _PyTime_FromSecondsObject()
* Add _PyTime_AsNanosecondsObject() and _testcapi.pytime_fromsecondsobject()
* Add unit tests
2015-03-27 17:12:45 +01:00
8c8b4e0ebf
Issue #11188 , #19748 : mktime() returns -1 on error. On Linux, the tm_wday field
...
is used as a sentinel () to detect if -1 is really an error or a valid
timestamp. On AIX, tm_wday is unchanged even on success and so cannot be used
as a sentinel.
2014-02-21 23:54:32 +01:00
1ac42614e3
Issue #19748 : On AIX, time.mktime() now raises an OverflowError for year
...
outsize range [1902; 2037].
2014-02-21 09:27:17 +01:00
3c1b379ebd
Issue #20320 : select.select() and select.kqueue.control() now round the timeout
...
aways from zero, instead of rounding towards zero.
It should make test_asyncio more reliable, especially test_timeout_rounding() test.
2014-02-17 00:02:43 +01:00
f28ba369dd
Issue #20532 : Tests which use _testcapi now are marked as CPython only.
2014-02-07 10:10:55 +02:00
5cfc79deae
Issue #20532 : Tests which use _testcapi now are marked as CPython only.
2014-02-07 10:06:39 +02:00
393a94243f
Issue #20101 : Merge with 3.3
2014-01-02 09:43:09 -06:00
487aedb77c
Issue #20101 : Allow test_monotonic to pass on Windows machines on which
...
time.get_clock_info('monotonic').resolution == 0.015600099999999999
This is just a workaround pending a real resolution to #20101 .
2014-01-02 09:41:10 -06:00
a4275b276c
(Merge 3.3) Close #19999 : tolerate coarse time when testing time.monotonic() on
...
very busy/slow buildbot
2013-12-16 22:38:46 +01:00
170078804c
Close #19999 : tolerate coarse time when testing time.monotonic() on very
...
busy/slow buildbot
2013-12-16 22:36:50 +01:00
101d9e7250
Issue 19572: More silently skipped tests explicitly skipped.
2013-12-08 00:44:27 -06:00
9fe6d86709
Issue 19572: More silently skipped tests explicitly skipped.
2013-12-08 00:20:35 -06:00
b5d386314f
Issue #19545 : Avoid chained exceptions while passing stray % to
...
time.strptime(). Initial patch by Claudiu Popa.
2013-11-24 18:17:11 +02:00
cdac302af3
Issue #19545 : Avoid chained exceptions while passing stray % to
...
time.strptime(). Initial patch by Claudiu Popa.
2013-11-24 18:15:37 +02:00
6c86181cd1
Issue #19715 : Ensure that consecutive calls to monotonic() are monotonic
2013-11-23 00:15:27 +01:00
a9c99a6119
test_time.test_monotonic(): use a longer sleep to try to make the test more reliable
2013-07-03 23:07:37 +02:00
3836d70ed5
#17690 : test_time now works with unittest test discovery. Patch by Zachary Ware.
2013-04-11 20:29:42 +03:00
0f38908684
#17572 : Avoid chained exceptions while passing bad directives to time.strptime(). Initial patch by Claudiu Popa.
2013-04-04 02:09:20 +03:00
5b89840d9c
Issue #16714 : use 'raise' exceptions, don't 'throw'.
...
Patch by Serhiy Storchaka.
2012-12-18 21:26:36 +02:00
737fb89dd1
Issue #16714 : use 'raise' exceptions, don't 'throw'.
...
Patch by Serhiy Storchaka.
2012-12-18 21:14:22 +02:00
c142bba2a7
Issue #1667546 : On platforms supporting tm_zone and tm_gmtoff fields
...
in struct tm, time.struct_time objects returned by time.gmtime(),
time.localtime() and time.strptime() functions now have tm_zone and
tm_gmtoff attributes. Original patch by Paul Boddie.
2012-06-13 22:15:26 -04:00
6222d76952
Fix test_time for adjusted/adjustable changes
2012-06-12 23:04:11 +02:00
2b89fdf7eb
PEP 418: Rename adjusted attribute to adjustable in time.get_clock_info() result
...
Fix also its value on Windows and Linux according to its documentation:
"adjustable" indicates if the clock *can be* adjusted, not if it is or was
adjusted.
In most cases, it is not possible to indicate if a clock is or was adjusted.
2012-06-12 22:46:37 +02:00
0dec1bfef9
Fix sporadic failure of test_time.test_process_time() on Windows
...
Use a threshold of 20 ms instead of 10 ms.
2012-06-01 22:45:23 +02:00
1c5ae55c85
don't use assertEqual for test for bool equality
2012-05-01 11:14:32 -04:00
49a69e4d48
strip is_ prefixes on clock_info fields
2012-05-01 09:38:34 -04:00
9a8ad0c5ea
Issue #14428 : Remove test_process_time_threads() from test_time
...
The test is unstable and it's not really interesting to test exactly how
threads are handled.
2012-04-30 01:39:57 +02:00
5df72c2c27
Issue #14428 : Make test_process_time_threads() less strict
2012-04-30 00:51:31 +02:00
1fc3ec91cc
Issue #14428 : Rewrite test_process_time_threads() test
...
time.process_time() is CPU time, not a number of seconds.
2012-04-29 19:46:19 +02:00
ec89539ccc
Issue #14428 , #14397 : Implement the PEP 418
...
* Rename time.steady() to time.monotonic()
* On Windows, time.monotonic() uses GetTickCount/GetTickCount64() instead of
QueryPerformanceCounter()
* time.monotonic() uses CLOCK_HIGHRES if available
* Add time.get_clock_info(), time.perf_counter() and time.process_time()
functions
2012-04-29 02:41:27 +02:00
30d79471bb
Expose clock_settime() as time.clock_settime()
2012-04-03 00:45:07 +02:00
071eca3f5c
Issue #10278 : Add an optional strict argument to time.steady(), False by default
2012-03-15 01:17:09 +01:00
ec919cc74d
Issue #10278 : Drop time.monotonic() function, rename time.wallclock() to time.steady()
...
* On Mac OS X, time.steady() now uses mach_absolute_time(), a monotonic clock
* Optimistic change: bet that CLOCK_MONOTONIC and CLOCK_REALTIME are available
when clock_gettime() is available
* Rewrite time.steady() documentation
2012-03-15 00:58:32 +01:00
5d272cc6a2
Close #14180 : Factorize code to convert a number of seconds to time_t, timeval or timespec
...
time.ctime(), gmtime(), time.localtime(), datetime.date.fromtimestamp(),
datetime.datetime.fromtimestamp() and datetime.datetime.utcfromtimestamp() now
raises an OverflowError, instead of a ValueError, if the timestamp does not fit
in time_t.
datetime.datetime.fromtimestamp() and datetime.datetime.utcfromtimestamp() now
round microseconds towards zero instead of rounding to nearest with ties going
away from zero.
2012-03-13 13:35:55 +01:00
643cd68ea4
Issue #13964 : signal.sigtimedwait() timeout is now a float instead of a tuple
...
Add a private API to convert an int or float to a C timespec structure.
2012-03-02 22:54:03 +01:00
4195b5caea
Backout f8409b3d6449: the PEP 410 is not accepted yet
2012-02-08 23:03:19 +01:00
Victor Stinner
Steve Dower
Larry Hastings
Serhiy Storchaka
Zachary Ware
Ezio Melotti
Andrew Svetlov
Alexander Belopolsky
Benjamin Peterson
Victor Stinner
Victor Stinner