* Modify DEFAULT_CONFIG for AIX

* bedevere/news did not like old name

* Modify NEWS entry

* Modified per peer review

* Define and use NULL_STR constant to account for AIX libc behavior

* Modify per peer review

* Modify NEWS

Assume tzname exists. Only use a hack to compute altzone if it's not defined.

* Skip posix_spawn scheduler tests on BSD. We were already skyping similar tests as the behaviour can depend on the implementation in some cases.

When os.fork() is called (on platforms that support it) all threads but the current one are destroyed in the child process. Consequently we must ensure that all but the associated interpreter are likewise destroyed. The main interpreter is critical for runtime operation, so we must ensure that fork only happens in the main interpreter.

https://bugs.python.org/issue34651

* bpo-33649: Refresh Tasks and Futures pages

* Fixes

* Fix markup

Co-authored-by: Benjamin Peterson <benjamin@python.org>

* small clarification

* edits to protocols doc

* Edit async queue doc

bpo-6721: When os.fork() was called while another thread holds a logging lock, the child process may deadlock when it tries to log.  This fixes that by acquiring all logging locks before fork and releasing them afterwards.

A regression test that fails before this change is included.

Within the new unittest itself: There is a small _potential_ due to mixing of fork and a thread in the child process if the parent's thread happened to hold a non-reentrant library call lock (malloc?) when the os.fork() happens.  buildbots and time will tell if this actually manifests itself in this test or not.  :/  A functionality test that avoids that would be a challenge.

An alternate test that isn't trying to produce the deadlock itself but just checking that the release and acquire calls are made would be the next best alternative if so.

Some updates to ancient text about comparisons; fixes bp-34552.

Second pass for asyncio subprocess and sync docs.


https://bugs.python.org/issue33649

This test is doesn't work when the test process is privledged, which is hard to detect.





https://bugs.python.org/issue34668

This function was not in any .h file and was not used by Python, so removing it is safe.


https://bugs.python.org/issue34653