Add missing 3.10/11 attributes to traceback module docs by Jackenmen · Pull Request #105043 · python/cpython

…ecorated with `@runtime_checkable` (pythonGH-102937)

(cherry picked from commit 58d2b30)

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

…onGH-102601)

(cherry picked from commit bd06375)

Co-authored-by: Dong-hee Na <donghee.na@python.org>

…strings (pythonGH-102979)

(cherry picked from commit 7f01a11)

Co-authored-by: Raymond Hettinger <rhettinger@users.noreply.github.com>

(cherry picked from commit d494091)

Co-authored-by: Raymond Hettinger <rhettinger@users.noreply.github.com>

pythonGH-102981)

(cherry picked from commit ded9a7f)

Co-authored-by: gaogaotiantian <gaogaotiantian@hotmail.com>

(cherry picked from commit 027223d)

Co-authored-by: gaogaotiantian <gaogaotiantian@hotmail.com>

…honGH-95495) (python#103006)

pythonGH-25309 enabled SSL_OP_IGNORE_UNEXPECTED_EOF by default, with a comment
that it restores OpenSSL 1.1.1 behavior, but this wasn't quite right.
That option causes OpenSSL to treat transport EOF as the same as
close_notify (i.e. SSL_ERROR_ZERO_RETURN), whereas Python actually has
distinct SSLEOFError and SSLZeroReturnError exceptions. (The latter is
usually mapped to a zero return from read.) In OpenSSL 1.1.1, the ssl
module would raise them for transport EOF and close_notify,
respectively. In OpenSSL 3.0, both act like close_notify.

Fix this by, instead, just detecting SSL_R_UNEXPECTED_EOF_WHILE_READING
and mapping that to the other exception type.

There doesn't seem to have been any unit test of this error, so fill in
the missing one. This had to be done with the BIO path because it's
actually slightly tricky to simulate a transport EOF with Python's fd
based APIs. (If you instruct the server to close the socket, it gets
confused, probably because the server's SSL object is still referencing
the now dead fd?)
(cherry picked from commit 420bbb7)

Co-authored-by: David Benjamin <davidben@google.com>

…python#103075)

There are some warnings if build python via clang:

Parser/pegen.c:812:31: warning: a function declaration without a prototype is deprecated in all versions of C [-Wstrict-prototypes]
_PyPegen_clear_memo_statistics()
                              ^
                               void

Parser/pegen.c:820:29: warning: a function declaration without a prototype is deprecated in all versions of C [-Wstrict-prototypes]
_PyPegen_get_memo_statistics()
                            ^
                             void

Fix it to make clang happy.

(cherry picked from commit 7703def)

Signed-off-by: Chenxi Mao <chenxi.mao@suse.com>
Co-authored-by: Chenxi Mao <chenxi.mao@suse.com>

(cherry picked from commit fda95aa)

Co-authored-by: Shantanu <12621235+hauntsaninja@users.noreply.github.com>

(cherry picked from commit c1e71ce)

Co-authored-by: gaogaotiantian <gaogaotiantian@hotmail.com>

(cherry picked from commit 55decb7)

Co-authored-by: Nouran Ali <nouranalimohammed@gmail.com>

fix FlagBoundary statements
add warning about reloading modules and enum identity
(cherry picked from commit 5ffc1e5)

Co-authored-by: Ethan Furman <ethan@stoneleaf.us>

…_init__ (pythonGH-103149)

(cherry picked from commit 2a4d8c0)

Co-authored-by: Ethan Furman <ethan@stoneleaf.us>

…me display on how to workaround the macOS 13 Ventura “The installer encountered an error” failure. pythonGH-103252)