traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
88,407 Commits 9 Branches 456 Tags 1.7 GiB
Commit Graph

123 Commits

Author SHA1 Message Date
Victor Stinner 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
Victor Stinner 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
Victor Stinner 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
Serhiy Storchaka f28ba369dd Issue #20532: Tests which use _testcapi now are marked as CPython only. 2014-02-07 10:10:55 +02:00
Serhiy Storchaka 5cfc79deae Issue #20532: Tests which use _testcapi now are marked as CPython only. 2014-02-07 10:06:39 +02:00
Zachary Ware 393a94243f Issue #20101: Merge with 3.3 2014-01-02 09:43:09 -06:00
Zachary Ware 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
Victor Stinner 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
Victor Stinner 170078804c Close #19999: tolerate coarse time when testing time.monotonic() on very 
busy/slow buildbot
 2013-12-16 22:36:50 +01:00
Zachary Ware 101d9e7250 Issue 19572: More silently skipped tests explicitly skipped. 2013-12-08 00:44:27 -06:00
Zachary Ware 9fe6d86709 Issue 19572: More silently skipped tests explicitly skipped. 2013-12-08 00:20:35 -06:00
Serhiy Storchaka 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
Serhiy Storchaka 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
Victor Stinner 6c86181cd1 Issue #19715: Ensure that consecutive calls to monotonic() are monotonic 2013-11-23 00:15:27 +01:00
Victor Stinner 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
Ezio Melotti 3836d70ed5 #17690: test_time now works with unittest test discovery. Patch by Zachary Ware. 2013-04-11 20:29:42 +03:00
Ezio Melotti 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
Andrew Svetlov 5b89840d9c Issue #16714: use 'raise' exceptions, don't 'throw'. 
Patch by Serhiy Storchaka.
 2012-12-18 21:26:36 +02:00
Andrew Svetlov 737fb89dd1 Issue #16714: use 'raise' exceptions, don't 'throw'. 
Patch by Serhiy Storchaka.
 2012-12-18 21:14:22 +02:00
Alexander Belopolsky 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
Victor Stinner 6222d76952 Fix test_time for adjusted/adjustable changes 2012-06-12 23:04:11 +02:00
Victor Stinner 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
Victor Stinner 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
Benjamin Peterson 1c5ae55c85 don't use assertEqual for test for bool equality 2012-05-01 11:14:32 -04:00
Benjamin Peterson 49a69e4d48 strip is_ prefixes on clock_info fields 2012-05-01 09:38:34 -04:00
Victor Stinner 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
Victor Stinner 5df72c2c27 Issue #14428: Make test_process_time_threads() less strict 2012-04-30 00:51:31 +02:00
Victor Stinner 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
Victor Stinner 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
Victor Stinner 30d79471bb Expose clock_settime() as time.clock_settime() 2012-04-03 00:45:07 +02:00
Victor Stinner 071eca3f5c Issue #10278: Add an optional strict argument to time.steady(), False by default 2012-03-15 01:17:09 +01:00
Victor Stinner 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
Victor Stinner 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
Victor Stinner 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
Victor Stinner 4195b5caea Backout f8409b3d6449: the PEP 410 is not accepted yet 2012-02-08 23:03:19 +01:00
Victor Stinner ccd5715a14 PEP 410 2012-02-08 14:31:50 +01:00
Victor Stinner 8b30201f7d Issue #13846: Add time.monotonic(), monotonic clock. 2012-02-07 23:29:46 +01:00
Victor Stinner 2d6251c7f7 Issue #13847: Fix test_time, time.gmtime() doesn't use localtime() 
On Windows, localtime(-1) fails, but not gmtime(1).
 2012-01-30 00:23:32 +01:00
Victor Stinner 53d3645f95 Issue #13847: Make test_localtime_failure() more robust 
Skip the test if we are unable to find an invalid time_t value.
 2012-01-27 01:03:25 +01:00
Victor Stinner 2cbae98ea4 Issue #13847: Fix test_mktime(), time.localtime() now raises OSError 2012-01-27 00:50:33 +01:00
Victor Stinner c1b5d34ede Issue #13847: time.localtime() and time.gmtime() now raise an OSError instead 
of ValueError on failure. time.ctime() and time.asctime() now raises an
OSError if localtime() failed.
 2012-01-27 00:08:48 +01:00
Victor Stinner 4ccc727793 Issue #10278: wallclock() cannot go backward, but two consecutive calls 
may return the same time.
 2012-01-23 23:48:41 +01:00
Victor Stinner 2dd254d17a Issue #10278: Be more explicit in tests than wallclock() is monotonic (cannot 
go backward)
 2012-01-20 02:24:18 +01:00
Antoine Pitrou 391166fbfc Be more lenient in test_wallclock (issue #10278). 2012-01-18 22:35:21 +01:00
Victor Stinner b94b266cfc Close #10278: Add time.wallclock() function, monotonic clock. 2012-01-18 01:50:21 +01:00
Victor Stinner 10a6ddb062 Issue #11886: Fix also test_time for the non-DST timezone name (EST/AEST) 2011-12-10 14:37:53 +01:00
Victor Stinner bc9f0c68f5 (Merge 3.2) Issue #11886: workaround an OS bug (time zone data) in test_time 
Australian Eastern Standard Time (UTC+10) is called "EST" (as Eastern Standard
Time, UTC-5) instead of "AEST" on some operating systems (e.g. FreeBSD), which
is wrong. See for example this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=93810
 2011-12-08 00:33:14 +01:00
Victor Stinner 0cd479074d Issue #11886: workaround an OS bug (time zone data) in test_time 
Australian Eastern Standard Time (UTC+10) is called "EST" (as Eastern Standard
Time, UTC-5) instead of "AEST" on some operating systems (e.g. FreeBSD), which
is wrong. See for example this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=93810
 2011-12-08 00:32:51 +01:00
Florent Xicluna e54371e24c Use unittest.skipUnless to skip the test related to the glibc bug, issue #13309. 2011-11-11 18:59:30 +01:00
Antoine Pitrou b0a1d628b8 Avoid a glibc bug in test_time (issue #13309) 2011-11-11 03:04:35 +01:00