Upgrade boto versions to support Python 3.12 and 3.13 #97
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 raises the boto3 and botocore version cap and fixes #95 .
boto3>=1.36
may use some AWS-specific APIs that are not compatible with our S3 endpoint -- this may be an issue after Python 3.14. I also noticed that some versions ofurllib=1.25.*
, which were required by the previous boto version pins, are actually incompatible with the newer versions of botocore, though they are incorrectly marked as compatible.This PR does not:
setup.py
, which I believe is where dependencies are read for wheels (please correct if I'm wrong)Neither should be hard to change.
Some tests still fail inconsistently because objects are not found after being uploaded, e.g.
(I see #96 tries to fix this, though I haven't tried it here.) I'm not sure if these errors are worse with the newer boto/urllib versions, or if it's worse with our endpoint specifically, but Python 3.9 seems to be consistently ok.