Thanks Ben Hoyt for the report.

getentropy() is used (OpenBSD 5.6+).

(OpenBSD 5.6+).

implementation is used.

using the C volatile keyword.

Add _Py_fstat_noraise() function when a Python exception is not welcome.

MemoryError.

MemoryError.

non-integer input.

Use _PyTime_ROUND_FLOOR and _PyTime_ROUND_CEILING instead.

This mimics get_param's error handling for the most part.  It is slightly
better in some regards as get_param can produce some really weird results for
duplicate *0* parts.  It departs from get_param slightly in that if we have a
mix of non-extended and extended pieces for the same parameter name, the new
parser assumes they were all supposed to be extended and concatenates all the
values, whereas get_param always picks the non-extended parameter value.  All
of this error recovery is pretty much arbitrary decisions...

All these functions only accept positive timeouts, so this change has no effect
in practice.

Add also more tests for ROUNd_FLOOR.

calls fstat() once. Before fstat() was called twice, which was not necessary.

check that microseconds and nanoseconds fits into the specified range.

Add _PyTime_AsTimeval_noraise() function. Call it when it's not possible (or
not useful) to raise a Python exception on overflow.

Don't call _Py_open() from _close_open_fds_safe() because it is call just after
fork(). It's not good to play with locks (the GIL) between fork() and exec().

Use instead _Py_open_noraise() which doesn't touch to the GIL.

datetime.time: round towards minus infinity ("floor") instead of rounding
towards zero ("down").

infinity (-inf) instead of rounding towards zero.

Replace _PyTime_ROUND_DOWN with _PyTime_ROUND_FLOOR.

- _PyTime_ObjectToTime_t()
- _PyTime_ObjectToTimespec()
- _PyTime_ObjectToTimeval()

directories are left after running a test.

* Remove _PyTime_gettimeofday()
* Add _PyTime_GetSystemClock()

directories are left after running a test.

now is non-modifiable mapping.

Also deprecate the undocumented set argument instead of removing
it already in 3.5.

Initial patch by Demian Brecht.

Previously, if you hit ctl-c while the pager was active, the python that
launched the subprocess for the pager would see the KeyboardInterrupt in the
__exit__ method of the subprocess context manager where it was waiting for the
subprocess to complete, ending the wait.  This would leave the pager running,
while the interactive interpreter, after handling the exception by printing
it, would go back to trying to post a prompt...but the pager would generally
have the terminal in raw mode, and in any case would be still trying to read
from stdin.  On some systems, even exiting python at that point would not
restore the terminal mode.  The problem with raw mode could also happen if
ctl-C was hit when pydoc was called from the shell command line and the pager
was active.

Instead, we now wait on the subprocess in a loop, ignoring KeyboardInterrupt
just like the pager does, until the pager actually exits.

(Note: this was a regression relative to python2...in python2 the pager
is called via system, and system does not return until the pager exits.)