Also added several regression tests.

os.urandom() has now one unique implementation, posix_urandom() which
calls _PyOS_URandom(). _PyOS_URandom() uses RAND_pseudo_bytes() on VMS.

Use 'srcdir' from sysconfig instead of 'projectbase' to build a
path to the Tools directory.  'projectbase' is the path of the build
directory, not the source directory.

The gdb hooks for debugging CPython (within Tools/gdb) have
been enhanced to show information on more C frames relevant to CPython within
the "py-bt" and "py-bt-full" commands:
  * C frames that are waiting on the GIL
  * C frames that are garbage-collecting
  * C frames that are due to the invocation of a PyCFunction

(helps getting results in real-time when stdio is transmitted over a pipe or socket)

(helps getting results in real-time when stdio is transmitted over a pipe or socket)

correct inconsistent profiles for multi-threaded programs.

Patch by Stefan Mihaila.

Patch by Stefan Mihaila.

python executable

The __os_install_macro defines some post-processing activities during an rpm
build; one of the scripts it calls is brp-python-bytecompile, which can take
an argument: the python executable with which to byte-compile .py files in the
package payload.

In some older versions of rpm (e.g. in RHEL 6), this invocation doesn't pass
in an argument, and brp-python-bytecompile defaults to using /usr/bin/python,
which can lead to the .py files being byte-compiled for the wrong version of
python.  This has been fixed in later versions of rpm by passing in
%{__python} as an argument to brp-python-bytecompile.

Workaround this by detecting if __os_install_post has a 0-argument invocation
of brp-python-bytecompile, and if so generating an equivalent macro that has
the argument, and explicitly provide the new definition within the specfile.

3.3 whatsnew: Comment out the section about new POSIX *at functions etc.; has to be rewritten later.

behind.