These appeared in commit c5ae169e.  The comment on them, as well as
the presence among them of a rule for the .gitignore file itself,
indicate that the author intended these lines to remain only in their
own local working tree -- not to get committed even to their own repo,
let alone merged upstream.

They did nevertheless get committed, because it turns out that Git
takes no notice of what .gitignore says about files that it's already
tracking... for example, this .gitignore file itself.

Give effect to these lines' original intention, by deleting them. :-)

Git tip, for reference: the `.git/info/exclude` file is a handy way
to do exactly what these lines were originally intended to do.  A
related handy file is `~/.config/git/ignore`.  See gitignore(5),
aka `git help ignore`, for details.



https://bugs.python.org/issue37936



Automerge-Triggered-By: @zware

It is deprecated since Python 3.4.

Declare Py_BytesMain() in Include/pylifecycle.h, rather in
Include/internal/pycore_pylifecycle.h.

For example, rename PyTuple_Fini() to _PyTuple_Fini().

These functions are only declared in the internal C API.

/cc @ambv since this needs to be included in 3.8 -- see https://github.com/pypa/pip/issues/6885.

Sorry about the last minute PR!


https://bugs.python.org/issue37664



Automerge-Triggered-By: @zooba

https://bugs.python.org/issue37055



Automerge-Triggered-By: @tiran

In a38e9d13 pyconfig.h.in was
manually edited and that edit was overwritten when running autoreconf.

* Restore running proactor event loop from non-main thread
Co-Authored-By: Kyle Stanley <aeros167@gmail.com>

It emits a deprecation warning and calls corresponding method
visit_Num(), visit_Str(), etc.

https://bugs.python.org/issue37805



Automerge-Triggered-By: @methane

Cease turning SyntaxWarnings into SyntaxErrors.

In case it has been previously created.

Co-authored-by: Andrew Nester <andrew.nester.dev@gmail.com>

- drop TargetScopeError in favour of raising SyntaxError directly
  as per the updated PEP 572
- comprehension iteration variables are explicitly local, but
  named expression targets in comprehensions are nonlocal or
  global. Raise SyntaxError as specified in PEP 572
- named expression targets in the outermost iterable of a
  comprehension have an ambiguous target scope. Avoid resolving
  that question now by raising SyntaxError. PEP 572
  originally required this only for cases where the bound name
  conflicts with the iteration variable in the comprehension,
  but CPython can't easily restrict the exception to that case
  (as it doesn't know the target variable names when visiting
  the outermost iterator expression)

Fix assert statement misbehavior if AssertionError is shadowed.

These were caused by keeping around a reference to the Squeezer
instance and calling it's load_font() upon config changes, which
sometimes happened even if the shell window no longer existed.

This change completely removes that mechanism, instead having the
editor window properly update its width attribute, which can then
be used by Squeezer.

Redo of #15402 by GeeTransit and Kyle Stanley.

"Arguments may be integers... " could be misunderstand as they also
could be strings.

New wording makes it clear that arguments have to be integers.

modified:   Doc/library/datetime.rst



Automerge-Triggered-By: @pganssle

This reverts commit a50f0a4c.

Co-Authored-By: Antoine <43954001+awecx@users.noreply.github.com>