I feel that it'd be useful to "codify" which python versions we want to support for this library.
Looking at https://devguide.python.org/versions/, python3.7 will drop off support in July this year, and python3.11 has been officially released for a few months.
My suggesting is to provide a EoL + some buffer support after which we can safely remove it from the checks and be able to use the new features for the library (and playing our role in prodding library users to move off of unsupported and unsafe python version)
I feel that it'd be useful to "codify" which python versions we want to support for this library.
Looking at https://devguide.python.org/versions/, python3.7 will drop off support in July this year, and python3.11 has been officially released for a few months.
The only other python implementation we test and support is pypy which seems to have already removed pypy3.7 from their download page.
My suggesting is to provide a EoL + some buffer support after which we can safely remove it from the checks and be able to use the new features for the library (and playing our role in prodding library users to move off of unsupported and unsafe python version)