Support Python 3.11 and 3.12

[callumforrester]

Expected Behavior

Tests should pass for supported Python versions >=3.9

Current Behavior

Tests currently fail for Python >3.10

Context

Suggested by @mrakitin in #1664

[tacaswell]

With #1672 the tests pass locally for me with the CPython 3.12 branch.

[tacaswell]

Although if I run pytest with warnings as errors I get a bunch of .... interesting..... related failures due to not handleing exceptions an background threads.

[callumforrester]

Interesting, I'm seeing the following for 3.12:

FAILED bluesky/tests/test_utils.py::test_CallbackRegistry_1[class_method-False-True] - AssertionError: Incorrect number of signals

[tacaswell]

Interesting, in #1672 the py311 and py312 are passing, but the older ones are failing.

I never saw that failure locally...

[callumforrester]

@tacaswell Is there any policy on deprecation? Numpy hasn't supported 3.8 for almost a year: https://endoflife.date/numpy, perhaps we should drop it

[tacaswell]

We should follow https://numpy.org/neps/nep-0029-deprecation_policy.html / https://scientific-python.org/specs/spec-0000/ as closely as we can without causing critical operational problems for any of the facilities who are actively involved in the collaboration.

I'm not sure if we have that formalized anyplace though.

[prjemian]

Why doesn't numpy follow the Python supported versions schedule? Py3.8 is not yet EOL (happens later this year).

[tacaswell]

@prjemian read the NEP29 on SPEC0 text for the long answer. The short answer is we decided to support a slightly shorter time window of versions than "all versions of Python that are still getting security bug-fixes" upstream.

[callumforrester]

Done now #1672 is merged, will make another ticket for dropping 3.8 and 3.9