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.

outsize range [1902; 2037].

aways from zero, instead of rounding towards zero.

It should make test_asyncio more reliable, especially test_timeout_rounding() test.

time.get_clock_info('monotonic').resolution == 0.015600099999999999

This is just a workaround pending a real resolution to #20101.

busy/slow buildbot

time.strptime().  Initial patch by Claudiu Popa.

#17572: Avoid chained exceptions while passing bad directives to time.strptime().  Initial patch by Claudiu Popa.

Patch by Serhiy Storchaka.

Patch by Serhiy Storchaka.

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.

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.

Use a threshold of 20 ms instead of 10 ms.

The test is unstable and it's not really interesting to test exactly how
threads are handled.

time.process_time() is CPU time, not a number of seconds.

 * 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

 * 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

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.

Add a private API to convert an int or float to a C timespec structure.

On Windows, localtime(-1) fails, but not gmtime(1).

Skip the test if we are unable to find an invalid time_t value.

of ValueError on failure. time.ctime() and time.asctime() now raises an
OSError if localtime() failed.

may return the same time.

go backward)