* main: (24 commits)pythongh-98040: Move the Single-Phase Init Tests Out of test_imp (pythongh-102561)pythongh-83861: Fix datetime.astimezone() method (pythonGH-101545)pythongh-102856: Clean some of the PEP 701 tokenizer implementation (python#103634)pythongh-102856: Skip test_mismatched_parens in WASI builds (python#103633)pythongh-102856: Initial implementation of PEP 701 (python#102855)pythongh-103583: Add ref. dependency between multibytecodec modules (python#103589)pythongh-83004: Harden msvcrt further (python#103420)pythonGH-88342: clarify that `asyncio.as_completed` accepts generators yielding tasks (python#103626)pythongh-102778: IDLE - make sys.last_exc available in Shell after traceback (python#103314)pythongh-103582: Remove last references to `argparse.REMAINDER` from docs (python#103586)pythongh-103583: Always pass multibyte codec structs as const (python#103588)pythongh-103617: Fix compiler warning in _iomodule.c (python#103618)pythongh-103596: [Enum] do not shadow mixed-in methods/attributes (pythonGH-103600)pythonGH-100530: Change the error message for non-class class patterns (pythonGH-103576)pythongh-95299: Remove lingering setuptools reference in installer scripts (pythonGH-103613)  [Doc] Fix a typo in optparse.rst (python#103504)pythongh-101100: Fix broken reference `__format__` in `string.rst` (python#103531)pythongh-95299: Stop installing setuptools as a part of ensurepip and venv (python#101039)pythonGH-103484: Docs: add linkcheck allowed redirects entries for most cases (python#103569)pythongh-67230: update whatsnew note for csv changes (python#103598)  ...

This is a refactoring change that aims to simplify ``ensurepip``.Before it, this module had legacy infrastructure that made anassumption that ``ensurepip`` would be provisioning more then just asingle wheel. That assumption is no longer true since [[1]][[2]][[3]].In this change, the improvement is done around removing unnecessaryloops and supporting structures to change the assumptions to expectonly the bundled or replacement ``pip`` wheel.[1]:python@ece20db[2]:python#101039[2]:python#95299

This is a refactoring change that aims to simplify ``ensurepip``.Before it, this module had legacy infrastructure that made anassumption that ``ensurepip`` would be provisioning more then just asingle wheel. That assumption is no longer true since [[1]][[2]][[3]].In this change, the improvement is done around removing unnecessaryloops and supporting structures to change the assumptions to expectonly the bundled or replacement ``pip`` wheel.[1]:python@ece20db[2]:python#101039[3]:python#95299

This is a refactoring change that aims to simplify ``ensurepip``.Before it, this module had legacy infrastructure that made anassumption that ``ensurepip`` would be provisioning more then just asingle wheel. That assumption is no longer true since [[1]][[2]][[3]].In this change, the improvement is done around removing unnecessaryloops and supporting structures to change the assumptions to expectonly the bundled or replacement ``pip`` wheel.[1]:python@ece20db[2]:python#101039[3]:python#95299

This is a refactoring change that aims to simplify ``ensurepip``.Before it, this module had legacy infrastructure that made anassumption that ``ensurepip`` would be provisioning more then just asingle wheel. That assumption is no longer true since [[1]][[2]][[3]].In this change, the improvement is done around removing unnecessaryloops and supporting structures to change the assumptions to expectonly the bundled or replacement ``pip`` wheel.[1]:python@ece20db[2]:python#101039[3]:python#95299

This is a refactoring change that aims to simplify ``ensurepip``.Before it, this module had legacy infrastructure that made anassumption that ``ensurepip`` would be provisioning more then just asingle wheel. That assumption is no longer true since [[1]][[2]][[3]].In this change, the improvement is done around removing unnecessaryloops and supporting structures to change the assumptions to expectonly the bundled or replacement ``pip`` wheel.[1]:python@ece20db[2]:python#101039[3]:python#95299

Currently `get-pip.py` installs not only pip, but also setuptools andwheel by default, unless the `--no-setuptools` / `--no-wheel` (or`PIP_NO_SETUPTOOLS` / `PIP_NO_WHEEL` env vars) are used.This has historically been necessary, however, modern versions of pipwill now fallback to `pyproject.toml` (PEP 517: [1]) based builds (whichwill default to a setuptools backend, and thus automatically installsetuptools and wheel in the isolated build environment) if eithersetuptools is not installed (as of pip 22.1: [2]), or if wheel is notinstalled (as of pip 23.1: [3]).In addition, as of Python 3.12, the stdlib's `ensurepip` and `venv`modules no longer install setuptools, and only install pip ([4]).As such, it is now time for `get-pip.py` to stop installing setuptoolsand wheel by default on Python 3.12+, in order to:- Act as another small step towards `pyproject.toml` / PEP 517  based builds eventually becoming the pip default.- Improve parity with the behaviour of `ensurepip` / `venv` on  Python 3.12+.- Allow `get-pip.py` to focus on its primary responsibility:  bootstrapping Pip.Closespypa#200.[1]:https://peps.python.org/pep-0517/[2]:pypa/pip#10717[3]:pypa/pip#11871[4]:python/cpython#101039

Currently `get-pip.py` installs not only pip, but also setuptools andwheel by default, unless the `--no-setuptools` / `--no-wheel` (or`PIP_NO_SETUPTOOLS` / `PIP_NO_WHEEL` env vars) are used.This has historically been necessary, however, modern versions of pipwill now fallback to `pyproject.toml` (PEP 517: [1]) based builds (whichwill default to a setuptools backend, and thus automatically installsetuptools and wheel in the isolated build environment) if eithersetuptools is not installed (as of pip 22.1: [2]), or if wheel is notinstalled (as of pip 23.1: [3]).In addition, as of Python 3.12, the stdlib's `ensurepip` and `venv`modules no longer install setuptools, and only install pip ([4]).As such, it is now time for `get-pip.py` to stop installing setuptoolsand wheel by default on Python 3.12+, in order to:- Act as another small step towards `pyproject.toml` / PEP 517  based builds eventually becoming the pip default.- Improve parity with the behaviour of `ensurepip` / `venv` on  Python 3.12+.- Allow `get-pip.py` to focus on its primary responsibility:  bootstrapping Pip.Closespypa#200.[1]:https://peps.python.org/pep-0517/[2]:pypa/pip#10717[3]:pypa/pip#11871[4]:python/cpython#101039

Currently `get-pip.py` installs not only pip, but also setuptools andwheel by default, unless the `--no-setuptools` / `--no-wheel` (or`PIP_NO_SETUPTOOLS` / `PIP_NO_WHEEL` env vars) are used.This has historically been necessary, however, modern versions of pipwill now fallback to `pyproject.toml` (PEP 517: [1]) based builds (whichwill default to a setuptools backend, and thus automatically installsetuptools and wheel in the isolated build environment) if eithersetuptools is not installed (as of pip 22.1: [2]), or if wheel is notinstalled (as of pip 23.1: [3]).In addition, as of Python 3.12, the stdlib's `ensurepip` and `venv`modules no longer install setuptools, and only install pip ([4]).As such, it is now time for `get-pip.py` to stop installing setuptoolsand wheel by default on Python 3.12+, in order to:- Act as another small step towards `pyproject.toml` / PEP 517  based builds eventually becoming the pip default.- Improve parity with the behaviour of `ensurepip` / `venv` on  Python 3.12+.- Allow `get-pip.py` to focus on its primary responsibility:  bootstrapping Pip.Closespypa#200.[1]:https://peps.python.org/pep-0517/[2]:pypa/pip#10717[3]:pypa/pip#11871[4]:python/cpython#101039

Currently `get-pip.py` installs not only pip, but also setuptools andwheel by default, unless the `--no-setuptools` / `--no-wheel` (or`PIP_NO_SETUPTOOLS` / `PIP_NO_WHEEL` env vars) are used.This has historically been necessary, however, modern versions of pipwill now fallback to `pyproject.toml` (PEP 517: [1]) based builds (whichwill default to a setuptools backend, and thus automatically installsetuptools and wheel in the isolated build environment) if eithersetuptools is not installed (as of pip 22.1: [2]), or if wheel is notinstalled (as of pip 23.1: [3]).In addition, as of Python 3.12, the stdlib's `ensurepip` and `venv`modules no longer install setuptools, and only install pip ([4]).As such, it is now time for `get-pip.py` to stop installing setuptoolsand wheel by default on Python 3.12+, in order to:- Act as another small step towards `pyproject.toml` / PEP 517  based builds eventually becoming the pip default.- Improve parity with the behaviour of `ensurepip` / `venv` on  Python 3.12+.- Allow `get-pip.py` to focus on its primary responsibility:  bootstrapping Pip.Closespypa#200.[1]:https://peps.python.org/pep-0517/[2]:pypa/pip#10717[3]:pypa/pip#11871[4]:python/cpython#101039

Currently the buildpack performs a system site-packages install of notonly pip, but also setuptools and wheel. This has historically beennecessary for pip to be able to build source distributions (sdists) forpackages that don't ship with compatible wheels.However:- Thanks to PEP 518, packages can now (and many already do) specify an  explicit build backend using `[build-system]` in their  `pyproject.toml`. The dependencies specified in that config (such as  setuptools and wheel) will be installed by pip into an isolated and  ephemeral build environment as part of the source distribution build  process. Such packages therefore don't need/use globally installed  setuptools/wheel versions.- As of pip v22.1, pip will now default to the isolated build environment  mode (along with a fallback legacy setuptools build backend), if the  setuptools package isn't installed globally. This means that packages  that haven't yet migrated to a PEP 518 `pyproject.toml` build backend  config can still build even if setuptools isn't installed globally.There are a small number of rarely used packages in the wild thataren't compatible with build isolation mode, however, these typicallyrequire more build dependencies than just setuptools, which means theywouldn't have worked with this buildpack anyway.As such, it's no longer necessary for us to install setuptools and wheelglobally. This matches the behaviour of the `venv` and `ensurepip` modulesin Python 3.12+, where setuptools and wheel installation has also beenremoved. And it also matches the default behaviour of Poetry too, whose`install --sync` command removes any implicitly installed packages in thecurrent environment (other than pip).See:https://peps.python.org/pep-0518/https://pip.pypa.io/en/stable/reference/build-system/https://pip.pypa.io/en/stable/reference/build-system/pyproject-toml/#build-isolationpypa/pip#10717python/cpython#101039pypa/get-pip#218astral-sh/uv#2252GUS-W-16437776.

Currently the buildpack performs a system site-packages install of notonly pip, but also setuptools and wheel. This has historically beennecessary for pip to be able to build source distributions (sdists) forpackages that don't ship with compatible wheels.However:- Thanks to PEP 518, packages can now (and many already do) specify an  explicit build backend using `[build-system]` in their  `pyproject.toml`. The dependencies specified in that config (such as  setuptools and wheel) will be installed by pip into an isolated and  ephemeral build environment as part of the source distribution build  process. Such packages therefore don't need/use globally installed  setuptools/wheel versions.- As of pip v22.1, pip will now default to the isolated build environment  mode (along with a fallback legacy setuptools build backend), if the  setuptools package isn't installed globally. This means that packages  that haven't yet migrated to a PEP 518 `pyproject.toml` build backend  config can still build even if setuptools isn't installed globally.There are a small number of rarely used packages in the wild thataren't compatible with build isolation mode, however, these typicallyrequire more build dependencies than just setuptools, which means theywouldn't have worked with this buildpack anyway.As such, it's no longer necessary for us to install setuptools and wheelglobally. This matches the behaviour of the `venv` and `ensurepip` modulesin Python 3.12+, where setuptools and wheel installation has also beenremoved. And it also matches the default behaviour of Poetry too, whose`install --sync` command removes any implicitly installed packages in thecurrent environment (other than pip).See:https://peps.python.org/pep-0518/https://pip.pypa.io/en/stable/reference/build-system/https://pip.pypa.io/en/stable/reference/build-system/pyproject-toml/#build-isolationpypa/pip#10717python/cpython#101039pypa/get-pip#218astral-sh/uv#2252GUS-W-16437776.

Currently the buildpack performs a system site-packages install of notonly pip, but also setuptools and wheel. This has historically beennecessary for pip to be able to build source distributions (sdists) forpackages that don't ship with compatible wheels.However:- Thanks to PEP 518, packages can now (and many already do) specify an  explicit build backend using `[build-system]` in their  `pyproject.toml`. The dependencies specified in that config (such as  setuptools and wheel) will be installed by pip into an isolated and  ephemeral build environment as part of the source distribution build  process. Such packages therefore don't need/use globally installed  setuptools/wheel versions.- As of pip v22.1, pip will now default to the isolated build environment  mode (along with a fallback legacy setuptools build backend), if the  setuptools package isn't installed globally. This means that packages  that haven't yet migrated to a PEP 518 `pyproject.toml` build backend  config can still build even if setuptools isn't installed globally.There are a small number of rarely used packages in the wild thataren't compatible with build isolation mode, however, these typicallyrequire more build dependencies than just setuptools, which means theywouldn't have worked with this buildpack anyway.As such, it's no longer necessary for us to install setuptools and wheelglobally. This matches the behaviour of the `venv` and `ensurepip` modulesin Python 3.12+, where setuptools and wheel installation has also beenremoved. And it also matches the default behaviour of Poetry too, whose`install --sync` command removes any implicitly installed packages in thecurrent environment (other than pip).See:https://peps.python.org/pep-0518/https://pip.pypa.io/en/stable/reference/build-system/https://pip.pypa.io/en/stable/reference/build-system/pyproject-toml/#build-isolationpypa/pip#10717python/cpython#101039pypa/get-pip#218astral-sh/uv#2252GUS-W-16437776.

It is necessary for building the package when running the integration tests,but more recent Python versions no longer include it by default:python/cpython#101039.