Name already in use

…3.2 (#100197)

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

)

* Quote paths in os.spawn tests on Windows so they work with spaces

* Add NEWS entry for os spawn test fix

* Fix code style to avoid double negative in os.spawn tests

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

---------

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

…3358)

Automerge-Triggered-By: GH:erlend-aasland

#103348)

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

Set `SHELL = /bin/sh -e` to ensure that complex recipes fail on the first error rather than incorrectly reporting success.

Co-authored-by: Zachary Ware <zach@python.org>

Co-authored-by: Artem Mukhin <ortem00@gmail.com>

…tic` in 'What's New in Python 3.12' (#103349)

…02813)

Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
Co-authored-by: Łukasz Langa <lukasz@langa.pl>

…_` (GH-102248)" (GH-103332)

This reverts commit aa0a73d.

…103286)


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

…opped (#93242)

Improve performance of `inspect.getattr_static`

…c` (#103318)

…ded (#103217)

…-103315)

This cleans things up a bit and simplifies adding new granular global locks.

…0 mode (#102518)

…dDuration (#103309)

…03293)

…in dark mode. (GH-103303)

The function is like Py_AtExit() but for a single interpreter.  This is a companion to the atexit module's register() function, taking a C callback instead of a Python one.

We also update the _xxinterpchannels module to use _Py_AtExit(), which is the motivating case.  (This is inspired by pain points felt while working on gh-101660.)

i.e. Color.RED.BLUE is now officially supported.

…103287)

Using the raw allocator for any of the global state makes sense, especially as we move to a per-interpreter obmalloc state (gh-101660).

…103280)

Several platforms don't define the static_assert macro despite having
compiler support for the _Static_assert keyword. The macro needs to be
defined since it is used unconditionally in the Python code. So it
should always be safe to define it if undefined and not in C++11 (or
later) mode.

Hence, remove the checks for particular platforms or libc versions,
and just define static_assert anytime it needs to be defined but isn't.
That way, all platforms that need the fix will get it, regardless of
whether someone specifically thought of them.

Also document that certain macOS versions are among the platforms that
need this.

The C2x draft (currently expected to become C23) makes static_assert
a keyword to match C++. So only define the macro for up to C17.

Co-authored-by: Victor Stinner <vstinner@python.org>