Currently CI is run with Python 3.8 and 3.9. However the latest supported Python version is 3.11 (according to the pyproject.toml file).
This is a problem because any breakage that occurs in Python 3.11 will not be detected by CI. For folks installing crystal from source via PyPI, such a breakage would be embarassing.
David wants CI to be run on Python 3.11 for at least one operating system to detect such breakages before users do.
Rabbit Holes
Adding Python 3.11 to the macOS matrix seems to trigger a problem with py2app
Adding a new Python version (like 3.11) to the Linux matrix in CI requires building a new wxPython wagon.
A step similar to "Install dependency wxPython from wagon (Python 3.9)" in push-github-action.yml will need to be created
Not providing a wagon will cause the install of wxPython to timeout, as shown in this CI run
Adding Python 3.11 to the Windows matrix works with windows-latest (as of 2024-06-09) but not windows-2019. Perhaps Python 3.11 isn't supported on Windows 2019?
Currently CI is run with Python 3.8 and 3.9. However the latest supported Python version is 3.11 (according to the pyproject.toml file).
This is a problem because any breakage that occurs in Python 3.11 will not be detected by CI. For folks installing crystal from source via PyPI, such a breakage would be embarassing.
David wants CI to be run on Python 3.11 for at least one operating system to detect such breakages before users do.
Rabbit Holes
windows-latest(as of 2024-06-09) but notwindows-2019. Perhaps Python 3.11 isn't supported on Windows 2019?