* Add News entry for the change in multiprocessing.reduction.recvfds
made in GH-9613.
(cherry picked from commit bd036d3d)
Co-authored-by: Pablo Galindo <Pablogsal@gmail.com>

https://bugs.python.org/issue34970
(cherry picked from commit 97cf0828)
Co-authored-by: Andrew Svetlov <andrew.svetlov@gmail.com>

For 3.7.1rc1 and 3.6.7rc1 we used a pre-release development
snapshot of Tk 8.6 to pick up some post-8.6.8 fixes for macOS.
But the snapshot introduced at least one regression (bpo-34927).
For rc2, revert to using the standard release 8.6.8 for now.
This reverts commit d9cfe5ed.

With macOS framework builds, test case test_nonexisting_script in
test_nonexisting_script fails because the test case assumes that
the file name in sys.executable will appear in the error message.
For macOS framework builds, sys.executable is the file name of the
stub launcher and its file name bears no relationship to the file
name of the actual python executable.  For now, skip the test in
this case.
(cherry picked from commit f6c29a65)
Co-authored-by: Ned Deily <nad@python.org>

(cherry picked from commit 4505f65a)
Co-authored-by: Gus Goulart <augusto@goulart.me>

(cherry picked from commit da2bf9f6)
Co-authored-by: Bruno Oliveira <nicoddemus@gmail.com>

(cherry picked from commit 65d2f8c0)
Co-authored-by: Zackery Spytz <zspytz@gmail.com>

(cherry picked from commit 53ebf4b0)
Co-authored-by: Zackery Spytz <zspytz@gmail.com>

(cherry picked from commit fc439d20)
Co-authored-by: Zackery Spytz <zspytz@gmail.com>

for the SHAKE algorithm in the hashlib module.
(cherry picked from commit 9b8c2e76)

It was proposed to add an warning for http.server regarding security
issues. The wording was provided at bpo-26005 by @orsenthil
(cherry picked from commit 1d26c72e)
Co-authored-by: Felipe Rodrigues <felipe@felipevr.com>

(cherry picked from commit 683281f5)

Add unit tests for the command line for the gzip module
(cherry picked from commit 84eec119)
Co-authored-by: Stéphane Wirtel <stephane@wirtel.be>

(cherry picked from commit c880ffe7)
Co-authored-by: twisteroid ambassador <twisteroidambassador@users.noreply.github.com>

When Python is built with the intel control-flow protection flags,
-mcet -fcf-protection, gdb is not able to read the stack without
actually jumping inside the function. This means an extra
'next' command is required to make the $pc (program counter)
enter the function and make the stack of the function exposed to gdb.
Co-Authored-By: Marcel Plch <gmarcel.plch@gmail.com>

(cherry picked from commit 9b7c74ca)
(cherry picked from commit 79d21331)
Co-authored-by: Victor Stinner <vstinner@redhat.com>

Let .chm document display non-ASCII characters properly

Escape the `body` part of .chm source file to 7-bit ASCII, to fix visual effect on some MBCS Windows systems.
(cherry picked from commit 6261ae9b)
Co-authored-by: animalize <animalize@users.noreply.github.com>

https://bugs.python.org/issue34901
(cherry picked from commit 656d52db)
Co-authored-by: Danish Prakash <grafitykoncept@gmail.com>

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.
(cherry picked from commit 19003841)

Co-authored-by: Gregory P. Smith <greg@krypto.org> [Google]

(cherry picked from commit d345bb4d)
Co-authored-by: Cheryl Sabella <cheryl.sabella@gmail.com>

(cherry picked from commit 7dfbd496)
Co-authored-by: Andrés Delfino <adelfino@gmail.com>

(cherry picked from commit cd45385f)

(cherry picked from commit ae62f015)
Co-authored-by: Zackery Spytz <zspytz@gmail.com>

* Documentation of UTC offset update
Since changes in the UTC offset that allows sub-minute offsets, the documentation needs update:

- "%z" format code documentation update
Karthikeyan Singaravelan commented on bugs.python.org:
Added as part of 018d353c and a fix regarding duplicate words for that part was added at bac2d5ba.
Relevant format string at https://github.com/python/cpython/pull/2896/filesGH-diff-25e2d173c84057d069b7890450714eddR214.
Relevant test case with 6-digit string for microsecond : https://github.com/python/cpython/pull/2896/filesGH-diff-acc40bec51c7de832de3361db3edae52R309.
Table at https://docs.python.org/3.7/library/datetime.htmlGH-strftime-and-strptime-behavior could also be updated with microseconds being optional in the second column
%z | UTC offset in the form ±HHMM[SS] (empty string if the object is naive). | (empty), +0000, -0400, +1030

- isoformat documentation update
According to me, needs confirmation:
Relevant format string at https://github.com/python/cpython/pull/4699/filesGH-diff-25e2d173c84057d069b7890450714eddR176
Relevant test case at https://github.com/python/cpython/pull/4699/filesGH-diff-25e2d173c84057d069b7890450714edd

* From Martin Panter: some style improvment;
From @pganssle: using f for fractional part of seconds in all file.
(cherry picked from commit 92878829)
Co-authored-by: Christophe Nanteuil <35002064+christopheNan@users.noreply.github.com>

[3.7] Make it clear that the msg argument to assertWarns/assertWarnsRegex/assertRaisesRegex is keyword-only. (GH-9680) (GH-9681)

A follow up to be4e5b89.
(cherry picked from commit e006b39a)
Co-authored-by: Benjamin Peterson <benjamin@python.org>

The docs were ambiguous about whether you pass in a coroutine function
or a coroutine object, e.g. is it:

  aestack.push_async_exit(some_async_func)

or

  aestack.push_async_exit(some_async_func())

(It's the first one.)
(cherry picked from commit a3c88ef1)
Co-authored-by: Nathaniel J. Smith <njs@pobox.com>

bpo-34565: Change a PC/launcher.c comment to accurately describe valid major versions. (GH-9037) (GH-9065)

(cherry picked from commit 3876af4f)
Co-authored-by: Brendan Gerrity <brerrity@gmail.com>

The _PyLong_FromByteArray() call in int_from_bytes_impl() was
unchecked.
(cherry picked from commit 7bb9cd0a)
Co-authored-by: Zackery Spytz <zspytz@gmail.com>

(cherry picked from commit addf8afb)

Fixes warnings in test added in bpo-34603.
(cherry picked from commit 4642d5f5)

(cherry picked from commit 4313a293)
Co-authored-by: Steve Dower <steve.dower@microsoft.com>

The added functions are as below :

| os module     | Pathlib       |
| ------------- | ------------- |
| os.chmod   | Path.chmod  |
| os.mkdir  | Path.mkdir  |
| os.rename | Path.rename |
| os.replace | Path.replace |
| os.rmdir  | Path.rmdir |
| os.remove, os.unlink | Path.unlink |
| os.path.samefile | Path.samefile |

Thanks

https://bugs.python.org/issue34825
(cherry picked from commit 6f9c55d1)
Co-authored-by: Xtreak <tirkarthi@users.noreply.github.com>

(cherry picked from commit 07fbbfde)
Co-authored-by: Stéphane Wirtel <stephane@wirtel.be>

(cherry picked from commit fc7d1b3b)
Co-authored-by: Matt Eaton <agnosticdev@gmail.com>

https://bugs.python.org/issue34871
(cherry picked from commit 6f85b826)
Co-authored-by: INADA Naoki <methane@users.noreply.github.com>

The C implementation of asyncio.Task currently fails to perform the
cancellation cleanup correctly in the following scenario.

    async def task1():
        async def task2():
            await task3     # task3 is never cancelled

        asyncio.current_task().cancel()
        await asyncio.create_task(task2())

The actuall error is a hardcoded call to `future_cancel()` instead of
calling the `cancel()` method of a future-like object.

Thanks to Vladimir Matveev for noticing the code discrepancy and to
Yury Selivanov for coming up with a pathological scenario..
(cherry picked from commit 548ce9dedd2e90945970671d441436a6a91608ab)
Co-authored-by: Elvis Pranskevichus <elvis@magic.io>


https://bugs.python.org/issue34872

formatfloat() was not checking if PyBytes_FromStringAndSize()
failed, which could lead to a null pointer dereference in
_PyBytes_FormatEx().
(cherry picked from commit 96c59327)
Co-authored-by: Zackery Spytz <zspytz@gmail.com>

Fix a reference issue inside multiprocessing.Pool that caused the pool to remain alive if it was deleted without being closed or terminated explicitly.
(cherry picked from commit 97bfe8d3)
Co-authored-by: tzickel <tzickel@users.noreply.github.com>