Upgrade to Python3.11

[NeonWizard]

Summary

Our internal build container uses Centos 9 which comes with Python 3.9 and unfortunately explicitly skips Python 3.10 in the package repositories, so we need to go up to Python 3.11

This is a good change to get ahead on though since Python 3.10 is reaching EOL this year (October 2026).

Test Plan

CI pipeline

[NeonWizard]

Sadly pyoxidizer only supports up to 3.10 (project was abandoned). Should be a non-issue tho

[NeonWizard]

Sadly pyoxidizer only supports up to 3.10 (project was abandoned). Should be a non-issue tho

(It was not a non-issue)

[luccabb]

Sadly pyoxidizer only supports up to 3.10 (project was abandoned). Should be a non-issue tho

We should be moving to 3.12 soon, this will bring pyinstaller and deprecate pyoxidizer for debian builds #31

[NeonWizard]

Sadly pyoxidizer only supports up to 3.10 (project was abandoned). Should be a non-issue tho

We should be moving to 3.12 soon, this will bring pyinstaller and deprecate pyoxidizer for debian builds #31

I believe the pyoxidizer build is also used in the Centos builder (for the RPMs). You'd have to get rid of pyoxidizer entirely

[luccabb]

I believe the pyoxidizer build is also used in the Centos builder (for the RPMs). You'd have to get rid of pyoxidizer entirely

you're correct. that's the plan

[luccabb]

Sadly pyoxidizer only supports up to 3.10 (project was abandoned). Should be a non-issue tho

(It was not a non-issue)

let's leave the pyoxidizer build unsupported until we figure out the 3.12 migration. the last version (py310) of gcm debians can be found at https://github.com/facebookresearch/gcm/releases/tag/v0.0.0

[NeonWizard]

Going to abandon this, found a workaround internally and we can just wait for the Python3.12 upgrade