(cherry picked from commit 85354ed7)

Co-authored-by: Alexey Izbyshev <izbyshev@ispras.ru>

Co-authored-by: Ezio Melotti <ezio.melotti@gmail.com>
Co-authored-by: blurb-it[bot] <43283697+blurb-it[bot]@users.noreply.github.com>
Co-authored-by: Łukasz Langa <lukasz@langa.pl>

The `utc_to_seconds` call can fail, here's a minimal reproducer on
Linux:

TZ=UTC python -c "from datetime import *; datetime.fromtimestamp(253402300799 + 1)"

The old behavior still raised an error in a similar way, but only
because subsequent calculations happened to fail as well. Better to fail
fast.

This also refactors the tests to split out the `fromtimestamp` and
`utcfromtimestamp` tests, and to get us closer to the actual desired
limits of the functions. As part of this, we also changed the way we
detect platforms where the same limits don't necessarily apply (e.g.
Windows).

As part of refactoring the tests to hit this condition explicitly (even
though the user-facing behvior doesn't change in any way we plan to
guarantee), I noticed that there was a difference in the places that
`datetime.utcfromtimestamp` fails in the C and pure Python versions, which
was fixed by skipping the "probe for fold" logic for UTC specifically —
since UTC doesn't have any folds or gaps, we were never going to find a
fold value anyway. This should prevent some failures in the pure python
`utcfromtimestamp` method on timestamps close to 0001-01-01.

There are two separate news entries for this because one is a
potentially user-facing change, the other is an internal code
correctness change that, if anything, changes some error messages. The
two happen to be coupled because of the test refactoring, but they are
probably best thought of as independent changes.

Fixes GH-91581
(cherry picked from commit 83c0247d)

Co-authored-by: Paul Ganssle <1377457+pganssle@users.noreply.github.com>

(cherry picked from commit 549567c6)

Co-authored-by: slateny <46876382+slateny@users.noreply.github.com>

gh-92530: Fix an issue that occurred after interrupting threading.Condition.notify (GH-92534) (GH-92831)

If Condition.notify() was interrupted just after it released the waiter lock,
but before removing it from the queue, the following calls of notify() failed
with RuntimeError: cannot release un-acquired lock.
(cherry picked from commit 70af994f)

Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>

(cherry picked from commit 3ed1cae9)

Co-authored-by: Stanley <46876382+slateny@users.noreply.github.com>

(cherry picked from commit 9f68dab3)

Co-authored-by: CAM Gerlach <CAM.Gerlach@Gerlach.CAM>

It fixes 252 errors from a Sphinx nitpicky run (sphinx-build -n). But
there's 8182 errors left.

Co-authored-by: Ezio Melotti <ezio.melotti@gmail.com>
(cherry picked from commit 664aa94b)

Co-authored-by: Julien Palard <julien@palard.fr>

[3.9] gh-92436: __future__ docs: add note on expectations for "from __future__ import annotations" (GH-92568). (#92726)

(cherry picked from commit 6582c964)

Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>

(cherry picked from commit b69297ea)

Co-authored-by: 狂男风 <CrazyBoyFeng@Live.com>

[3.9] gh-91810: ElementTree: Use text file's encoding by default in XML declaration (GH-91903) (GH-92665)



ElementTree method write() and function tostring() now use the text file's
encoding ("UTF-8" if not available) instead of locale encoding in XML
declaration when encoding="unicode" is specified.
(cherry picked from commit 707839b0)


Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>

Automerge-Triggered-By: GH:serhiy-storchaka

(cherry picked from commit 38486ca2)


Co-authored-by: Mikhail Terekhov <termim@gmail.com>

Automerge-Triggered-By: GH:serhiy-storchaka

[3.9] gh-76773: Update docs mentioning no-longer-supported Windows versions & features (GH-92529) (GH-92610)



(cherry picked from commit f1bbcba7)


Co-authored-by: CAM Gerlach <CAM.Gerlach@Gerlach.CAM>

Automerge-Triggered-By: GH:serhiy-storchaka

Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
Co-authored-by: Victor Stinner <vstinner@python.org>
(cherry picked from commit 4bd07d1d)

Co-authored-by: Erlend Egeberg Aasland <erlend.aasland@protonmail.com>

(cherry picked from commit c56e2bb9)

Co-authored-by: Cheryl Sabella <cheryl.sabella@gmail.com>

* [3.9] bpo-46785: Fix race condition between os.stat() and unlink on Windows (GH-31858).
(cherry picked from commit 39e6b8ae)

Co-authored-by: Itai Steinherz <itaisteinherz@gmail.com>

See: https://mail.python.org/archives/list/docs@python.org/thread/KDVFGNGGUGGPVRZT7WZYHHWXCRS2GEN7/


(cherry picked from commit b77a95f4)

Co-authored-by: Julien Palard <julien@palard.fr>

(cherry picked from commit f4e317b3)

Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com>

Signed-off-by: Erlend E. Aasland <erlend.aasland@protonmail.com>
(cherry picked from commit 3edda031)

Co-authored-by: Erlend Egeberg Aasland <erlend.aasland@protonmail.com>

* Some handlers were wrongly described as text-encoding only, but actually they can also be used in text-decoding.
* Add more description to each handler.
* Add two REPL examples.
* Add indexes for Error Handler's name.

Co-authored-by: Kyle Stanley <aeros167@gmail.com>
Co-authored-by: Victor Stinner <vstinner@python.org>
Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
(cherry picked from commit 5bc23902)

Co-authored-by: Ma Lin <animalize@users.noreply.github.com>

see https://github.com/gotcha/ipdb/issues/172



Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
(cherry picked from commit 2888b110)

Co-authored-by: Godefroid Chapelle <gotcha@bubblenet.be>

Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
(cherry picked from commit 859250cc)

Co-authored-by: slateny <46876382+slateny@users.noreply.github.com>

[3.10] gh-90622: Do not spawn ProcessPool workers on demand via fork method. (GH-91598) (GH-92497) (#92499)

Do not spawn ProcessPool workers on demand when they spawn via fork.

This avoids potential deadlocks in the child processes due to forking from
a multithreaded process..
(cherry picked from commit ebb37fc3)

Co-authored-by: Gregory P. Smith <greg@krypto.org>
(cherry picked from commit b795376a)

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

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

(cherry picked from commit 88831728)

Co-authored-by: Ezio Melotti <ezio.melotti@gmail.com>

(cherry picked from commit 318c4e91)

Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com>

[3.9] gh-92417: `json` docs: `dict` is ordered on all supported Python versions (GH-92422) (GH-92466)



(cherry picked from commit bc098cfd)


Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com>

Automerge-Triggered-By: GH:serhiy-storchaka

* Remove redundant footnote ref: the footnote has been removed
* Fix footnote ref to match footnote
* Convert footnotes into reST footnotes: will error if missing
(cherry picked from commit 788ef54b)


Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>

Automerge-Triggered-By: GH:serhiy-storchaka

(cherry picked from commit 8f293180)


Co-authored-by: slateny <46876382+slateny@users.noreply.github.com>

Automerge-Triggered-By: GH:serhiy-storchaka

Given that 2.7 has now been end-of-life for two and a half years,
I don't think we need such a detailed explanation here anymore of
the differences between Python 2 and Python 3.
(cherry picked from commit 8efda1e7)


Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com>

Automerge-Triggered-By: GH:serhiy-storchaka

gh-92417: `typing` docs: `from __future__ import annotations` can be used in all supported Python versions (GH-92418)

(cherry picked from commit e5b4bd4d)

Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com>

* Fix missing possessive apostrophe
(cherry picked from commit a79001ee)

Co-authored-by: gophra <105054704+gophra@users.noreply.github.com>

(cherry picked from commit 43b135f9)

Co-authored-by: Robert Howlett <robert@howletts.org.uk>

Co-authored-by: Robert Howlett <robert@howletts.org.uk>

(cherry picked from commit d707d073)

Co-authored-by: slateny <46876382+slateny@users.noreply.github.com>

Co-authored-by: slateny <46876382+slateny@users.noreply.github.com>

The current wording implied this, but didn't state it explicitly.
(cherry picked from commit 740da8d3)

Co-authored-by: Matt Wozniski <godlygeek@gmail.com>

They caused duplicated sections.
(cherry picked from commit 9b491ae0)

Co-authored-by: Inada Naoki <songofacandy@gmail.com>

* [3.9] gh-80254: Disallow recursive usage of cursors in `sqlite3` converters

(cherry picked from commit c908dc5b4798c311981bd7e1f7d92fb623ee448b)

Co-authored-by: Sergey Fedoseev <fedoseev.sergey@gmail.com>
Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>

* Fix ref leak in pysqlite_cursor_iternext

* Explicitly free resources at test tearDown()