Use Python 3.11

[jensens]

• Use Python 3.11
• Cleanup dependencies (Debian, pip), partially addresses check/remove superflous apt dependencies #89
• fixes Use GHCR for test image #75

[Rudd-O]

Extra twin turbo hotness.

[jensens]

The possible problem is, there are some packages with C-extensions in the Zope world pulled in and the image does not provide a build environment by default.

[jensens]

tests are passing, it is not working anyway.

[davisagli]

Having an image with Python 3.11 sounds good, but it is also a significant change. There may be addons or project code that is not compatible with it yet. Do we need to consider publishing images for multiple versions of Python?

[Rudd-O]

Having an image with Python 3.11 sounds good, but it is also a significant change. There may be addons or project code that is not compatible with it yet. Do we need to consider publishing images for multiple versions of Python?

I think the risk that code which worked with Python 3.9 and won't work with Python 3.11 is fairly low, and worth the benefits.

[jensens]

Two more thoughts:

• performance is much better
• green IT -> lower CO2 footprint

[davisagli]

I won't block this (I want to try Python 3.11 also). But I do think there is a nonzero chance we'll need to start building an image with Python 3.10 as well, for example if there are addons which are not compatible with Python 3.10 yet.

[jensens]

But I do think there is a nonzero chance we'll need to start building an image with Python 3.10 as well, for example if there are addons which are not compatible with Python 3.10 yet.

I think this is fine, but I would wait for complaints instead of providing one proactive. I go for merge.