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
ccd5715a14
PEP 410
2012-02-08 14:31:50 +01:00
8b30201f7d
Issue #13846 : Add time.monotonic(), monotonic clock.
2012-02-07 23:29:46 +01:00
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
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
2cbae98ea4
Issue #13847 : Fix test_mktime(), time.localtime() now raises OSError
2012-01-27 00:50:33 +01:00
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
4ccc727793
Issue #10278 : wallclock() cannot go backward, but two consecutive calls
...
may return the same time.
2012-01-23 23:48:41 +01:00
2dd254d17a
Issue #10278 : Be more explicit in tests than wallclock() is monotonic (cannot
...
go backward)
2012-01-20 02:24:18 +01:00
391166fbfc
Be more lenient in test_wallclock (issue #10278 ).
2012-01-18 22:35:21 +01:00
b94b266cfc
Close #10278 : Add time.wallclock() function, monotonic clock.
2012-01-18 01:50:21 +01:00
10a6ddb062
Issue #11886 : Fix also test_time for the non-DST timezone name (EST/AEST)
2011-12-10 14:37:53 +01:00
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
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
e54371e24c
Use unittest.skipUnless to skip the test related to the glibc bug, issue #13309 .
2011-11-11 18:59:30 +01:00
b0a1d628b8
Avoid a glibc bug in test_time (issue #13309 )
2011-11-11 03:04:35 +01:00
2fbc185209
Issue #13312 : skip the failing negative years for now.
2011-11-02 08:13:43 +01:00
dfee6c8dee
Actually, there's more than one failing value. (changeset 9cb1b85237a9, issue #13312 ).
2011-11-02 03:22:15 +01:00
e2a732e706
Issue #13312 : skip the single failing value for now.
2011-11-02 01:28:17 +01:00
d1bd7f7730
Additional tests for negative years.
2011-11-01 23:42:05 +01:00
725af4dc1d
Lowercase the test name, to run last.
2011-11-01 17:42:24 +01:00
050c7e64cd
Replace temporary tests with the real test case for issue #13309 on Gentoo.
2011-11-01 16:58:54 +01:00
712b14fc2a
Troubleshoot issue #13309 on Gentoo buildbot.
2011-11-01 16:07:23 +01:00
752c1d4c02
Add temporary tests to troubleshoot issue #13309 on Gentoo buildbot.
2011-11-01 15:12:34 +01:00
bceb528af5
Test the year range supported by time.strftime() and time.asctime().
2011-11-01 14:11:34 +01:00
49ce06858b
Strengthen the tests for format '%Y', in relation with issue #13305 .
2011-11-01 12:56:14 +01:00
e0be423297
Close #10278 : Add clock_getres(), clock_gettime() and CLOCK_xxx constants to
...
the time module. time.clock_gettime(time.CLOCK_MONOTONIC) provides a monotonic
clock
2011-10-25 13:06:09 +02:00
7f53a5027d
Issue #12459 : time.sleep() now raises a ValueError if the sleep length is
...
negative, instead of an infinite sleep on Windows or raising an IOError on
Linux for example, to have the same behaviour on all platforms.
2011-07-05 22:00:25 +02:00
03163ac185
Issue #11930 : Remove deprecated time.accept2dyear.
2011-05-02 12:20:52 -04:00
ae664fb528
Merge from 3.1
2011-04-06 14:11:09 +08:00
Victor Stinner
Ezio Melotti
Andrew Svetlov
Alexander Belopolsky
Benjamin Peterson
Victor Stinner
Victor Stinner
Antoine Pitrou
Florent Xicluna
Senthil Kumaran