Requiring a specific version of Python in CI actions is getting us into trouble when newer versions of packages either expect or require newer versions of python. The package might not get updated properly, because pip will hold it back.
Specify Python 3.x in this repos' CI actions, and in the cookiecutter actions it creates.
Set intersphinx_mapping to Python 3 instead of 3.4. Now that MicroPython has started implementing some selected features from later versions of Python, holding the doc back to 3.4 can be incorrect. We may as well keep up. It may still be wrong, but it is likely to be less wrong.
In the cookiecutter setup.py, specify compatibility simply as Python 3, instead of 3.4 and 3.5.
If this is approved, then the libraries should be updated in a sweep to use these changes.
Requiring a specific version of Python in CI actions is getting us into trouble when newer versions of packages either expect or require newer versions of python. The package might not get updated properly, because pip will hold it back.
3.xin this repos' CI actions, and in the cookiecutter actions it creates.intersphinx_mappingto Python 3 instead of 3.4. Now that MicroPython has started implementing some selected features from later versions of Python, holding the doc back to 3.4 can be incorrect. We may as well keep up. It may still be wrong, but it is likely to be less wrong.setup.py, specify compatibility simply as Python 3, instead of 3.4 and 3.5.If this is approved, then the libraries should be updated in a sweep to use these changes.