set beyond size.  Based on patch by John Leitch.

set beyond size.  Based on patch by John Leitch.

set beyond size.  Based on patch by John Leitch.

The ICC compiler doesn't seem to support defined() in macro expansion. Example
of warning:

warning #3199: "defined" is always false in a macro expansion in Microsoft mode

Reported by John Leitch and Bryce Darling, patch by Raymond Hettinger.

As suggested by Steve Dower and approved by Stefan Krah.

collection) in collections.OrderedDict constructor.

Patch reviewed by Serhiy Storchaka.

Only use it on the most important number. This change fixes also a compiler
warning on modf().

Ensure that the tv_nsec field is set, even if the function fails
with an overflow.

Handle PyCapsule_Import() failure (exception) in PyCodec_NameReplaceErrors():
return immedialty NULL.

Clear PyObject_Str() exception if it failed, ast_error() should not be called
with an exception set.

* Call _Py_CheckFunctionResult() to check for bugs in type
  constructors (tp_new)
* Add assertions to ensure an exception was raised if tp_init failed
  or that no exception was raised if tp_init succeed

Refactor also the function to have less indentation.

The support import is not needed in Python 3.5

datetime.datetime now round microseconds to nearest with ties going away from
zero (ROUND_HALF_UP), as Python 2 and Python older than 3.3, instead of
rounding towards -Infinity (ROUND_FLOOR).

eintr_tester.py calls signal.setitimer() to send signals to the current process
every 100 ms. The test sometimes hangs on FreeBSD. Maybe there is a race
condition in the child process after fork(). It's unsafe to run arbitrary code
after fork().

This change replace os.fork() with a regular call to subprocess.Popen(). This
change avoids the risk of having a child process which continue to execute
eintr_tester.py instead of exiting. It also ensures that the child process
doesn't inherit unexpected file descriptors by mistake.

Since I'm unable to reproduce the issue on FreeBSD, I will have to watch
FreeBSD buildbots to check if the issue is fixed or not.

Remove previous attempt to debug: remove call to
faulthandler.dump_traceback_later().

I was not supposed to commit the function with the name pymonotonic_new(). I
forgot to rename it.

Don't check anymore at runtime that the monotonic clock doesn't go backward.
Yes, it happens. It occurs sometimes each month on a Debian buildbot slave
running in a VM.

The problem is that Python cannot do anything useful if a monotonic clock goes
backward. It was decided in the PEP 418 to not fix the system, but only expose
the clock provided by the OS.