Drop support for python 3.8 & add 3.13 #929
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.
This PR drops support for the now EOL Python 3.8 (since 2024-09-06). Additionally, since we haven't done so yet, it also adds support for python 3.13 - moving the latest CI version & adding it to tox versions.
Additionally, this also performs some housekeeping tasks:
cffi
dependency, as the current version fails to build on MacOS with Python 3.13requests
dependency, as the currently installed version: 2.32.0 was marked as yanked, due to CVE-2024-35195.pythonVersion
config value of pyright to the oldest supported version (3.9), for some reason, this was set to 3.10 - I think this was done because pyright didn't support checking for__future__.annotations
before, and we decided we wanted to be able to utilize the newer typing syntax with it, so we used a more recent version to avoid the errors. However, since pyright does support__future__.annotations
now, this can be dropped back down.Note: #928 is currently blocked by this PR, as poetry 2.0 has dropped support for py 3.8