Check if we still need to use Python 3.6.10 in CI
alexjpwalker opened this issue · comments
Problem to Solve
We currently set the Python environment to version 3.6.10 with a pyenv command in automation.yml. But most users will be on Python 3.8 or 3.9 by now.
Proposed Solution
Try using Python 3.8 (or whatever is the standard when this issue is tackled).
Additional Information
We would ideally use whatever Python is installed in Grabl, thus eliminating the need for a pyenv call in this Grabl CI file.
This issue was tackled when we upgraded our Ubuntu images to 22.04.