Patch by Vlad Shcherbina

Patch by Vlad Shcherbina

Patch contributed by Vajrasky Kok. Addresses Issue #17324

Patch contributed by Vajrasky Kok. Addresses Issue #17324

if all necessary functions are already found in libuuid.
Patch by Evgeny Sologubov.

if all necessary functions are already found in libuuid.
Patch by Evgeny Sologubov.

- my previous removal and hg resolve mark had still left them and hooks did not catch it too!

Improve the docstring of random.shuffle. Inform users not to provide int arg.
Addresses issue #14927

Addresses issue #14927

Suggested by Wouter Bolsterlee.

Clarify mmap.close method  behavior.  Addresses issue  #18815
Patch contributed by Anoop Thomas Mathew.

Patch contributed by Anoop Thomas Mathew.

Document Fraction's numerator and denominator properties.
Addresses issue #18800

Addresses issue #18800

Due to recent changes, a Thread doesn't know that it's over before
someone calls .join() or .is_alive().  That meant repr(Thread)
continued to include "started" (and not "stopped") before one of
those methods was called, even if hours passed since the thread
ended.

Repaired that.

Antoine Pitrou found a variation that worked for him on the
thread+fork tests, and added an important

    self._is_stopped = True

to the after-fork code.  I confess I don't know why things passed
before.  But then mixing fork with threads is insane ;-)

Unixy buildbots were failing the thread + fork tests :-(

Documented some obscurities, and assert'ed ._stop()'s crucial precondition.

The fix for issue 18808 left us checking two things to be sure a Thread
was done:  an Event (._stopped) and a mutex (._tstate_lock).  Clumsy &
brittle.  This patch removes the Event, leaving just a happy lock :-)

The bulk of the patch removes two excruciating tests, which were
verifying sanity of the internals of the ._stopped Event after a fork.
Thanks to Antoine Pitrou for verifying that's the only real value
these tests had.

One consequence of moving from an Event to a mutex:  waiters (threads
calling Thread.join()) used to block each on their own unique mutex
(internal to the ._stopped event), but now all contend on the same
mutex (._tstate_lock).  These approaches have different performance
characteristics on different platforms.  I don't think it matters in
this context.

module is present (to record skipped tests)