Generally comparable perf for the "good" case where memchr doesn't
return any collisions (false matches on lower byte) but clearly faster
with collisions.

And it raises `make suspicious` false positives.

…H-93063)

…3066)

Also while there, clarify a few things about why we reduce the hash to 32 bits.

Co-authored-by: Eli Libman <eli@hyro.ai>
Co-authored-by: Yury Selivanov <yury@edgedb.com>
Co-authored-by: Łukasz Langa <lukasz@langa.pl>

Include member names in error message.

…pt ZIP file (GH-32291)

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

* fix issue 93010

Co-authored-by: blurb-it[bot] <43283697+blurb-it[bot]@users.noreply.github.com>

…-93007)

Update documentation of PyUnicode_DecodeFSDefault(),
PyUnicode_DecodeFSDefaultAndSize() and PyUnicode_EncodeFSDefault():
they now use the filesystem encoding and error handler of PyConfig,
Py_FileSystemDefaultEncoding and Py_FileSystemDefaultEncodeErrors
variables are no longer used.

Deprecate global configuration variables, like
Py_IgnoreEnvironmentFlag, in the documentation: the
Py_InitializeFromConfig() API should be instead.

- WASI's ``gethostname()`` is a stub that always fails with OSError
  ``ENOTSUP``
- skip mailcap ``test`` if subprocess is not available
- WASI process_time clock does not work.

This fixes an issue on tutorial/classes.rst section 9.4 where the example "class Warehouse"
was truncated when pressing the >>> button to hide the prompts and output.

Fixes #91061

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

Fixes #92994

Fixes #73137

See 35b98e3

Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>

Remove helper managed_connect(). Use memory_database() or
contextlib.closing() + addCleanup(unlink) instead.

Fixes #91362

* Test with with escaped non-ascii characters
* Test read-only open of existing DB.

…-92951)

…) to bytes (GH-93046)

Just pass it to the factory as is.

For example, instead of "eval()uated" (link from "eval()")
show "evaluated" (link from the whole word).

Fixes #93019

#72073

https://docs.python.org/3.12/library/pathlib.html#pathlib.Path.rename

…es (GH-92793)

As discussed in #92611 and #92564 and as a followup to PR #92612 , this 3.11+ only PR uses the proper `deprecated-removed` role for the modules deprecated by PEP 593 (PEP-594) to clearly indicate to users that a removal version is planned and what it is, so they can prepare accordingly or voice any unanticipated impacts.

Related to #92792 ; if we decide to backport that PR, the upgrade to using `deprecated-removed` on those functions can be moved to this one.