Maintenance: Update to Python 3.11

[amotl]

About

Just a humble attempt to modernize the Python version and the package dependencies.

Notes

Needs more love on different levels.

[SStorm]

Can we please go with 3.10 first - 3.11 is still a bit on the bleeding edge with some libraries being incompatible.

[SStorm]

Due to there not being a lockfile for setuptools, I am strongly against pinning version ranges - this eventually leads to some library releasing a patch version that breaks backwards compatibility accidentally and you no longer have predictable builds. Let's leave it like it was please.

[amotl]

I've removed the pinning of version ranges again.

[amotl]

Hi Romanas. Thanks. I was just playing around a bit, and I do not plan to submit this patch as a proposal for integration.

Can you share some pointers to the libraries being incompatible with Python 3.11 in one way or another, if you may know about the right spots already? It will tremendously help to get a better understanding.

[SStorm]

I only have anecdotal evidence, i.e. when we were trying to upgrade to 3.11 in the cloud-api, there were issues with celery. That made me come to a mental conclusion "3.11 is too early for us" and forget about it.

[amotl]

References about mypy modernizations, re. Error: no mypy cache directory.

• (🎁) Improve usability of --install-types python/mypy#10600 (comment)
• --install-types can mask failure details python/mypy#10768

[goat-ssh]

@amotl do you plan working on this one ?

[amotl]

Hi @goat-ssh. I can give the patch another refresh if there is interest.

[amotl]

References about mypy modernizations [...]

mypy needs to be bumped first I guess.

• See Maintenance: Update to mypy 1.11.2 #654.