Upgrade to Python 3.10; Upgrade Sphinx to 4.2.0 #501
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
ElastAlert 2 is pinned to Python 3, so whenever a new minor release of Python 3 is uploaded to Docker Hub, the next time ElastAlert 2 builds it will use the newer minor release. This is good in that it keeps ElastAlert 2 current, but when an incompatibility arises, the builds and tests fail. This occurred most recently with PR #499. That PR will not have a clean build until ElastAlert 2 is either back pinned to Python 3.9, or is upgraded to fully support Python 3.10.
This PR adds supports for Python 3.10, which required installing gcc and libffi-dev packages in order to build the cffi python wheel. Also, Sphinx 4.1.2 has an incompatibility with Python 3.10, which is fixed in Sphinx 4.2.0.
Checklist
make test-docker
with my changes.Questions or Comments