Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFC: Change setup.py to require older version of botocore with compatible implementation #1794

Merged
merged 1 commit into from
Aug 29, 2018

Conversation

garyd203
Copy link
Contributor

Mitigate #1793 by restricting maximum version for botocore.

botocore v1.11.0 changed it's internal implementation so that it now uses a different library for HTTP requests. This means that moto's mocking will not work, and test code will inadvertently call the live AWS service.

As an interim solution to reduce the impact of this breakage, we restrict the "required" (ie. recommended) version of botocore so that users will be less likely to use an incompatible version, and will receive a pip warning when they do.

botocore v1.11.0 changed it's internal implementation so that it now
uses a different library for HTTP requests. This means that moto's
mocking will not work, and test code will inadvertently call the live
AWS service.

As an interim solution to reduce the impact of this breakage, we
restrict the "required" (ie. recommended) version of botocore so that
users will be less likely to use an incompatible version, and will
receive a pip warning when they do.
@coveralls
Copy link

coveralls commented Aug 27, 2018

Coverage Status

Coverage decreased (-0.07%) to 92.339% when pulling abc15f0 on garyd203:1793-workaround into 9c6e7f2 on spulec:master.

@garyd203
Copy link
Contributor Author

Note to other readers - also read the discussion in #1793

@spulec spulec merged commit f7b039e into getmoto:master Aug 29, 2018
@spulec
Copy link
Collaborator

spulec commented Aug 29, 2018

Thanks @garyd203 for the help with all of this. Going to cut a release now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants