f66aee733b
botocore 1.3.29 (new as of yesterday) breaks a few of the s3 and lambda tests; something about a StringIO being closed prematurely. ¯\_(ツ)_/¯ boto3 doesn't pin the botocore version; as a result the new version of botocore gets pulled in transitively, breaking today's builds. Signed-off-by: Scott Greene <scott.greene@getbraintree.com>
13 lines
235 B
Plaintext
13 lines
235 B
Plaintext
-r requirements.txt
|
|
mock
|
|
nose
|
|
sure>=1.2.24
|
|
coverage
|
|
freezegun
|
|
flask
|
|
# botocore 1.3.29 breaks s3 in tests (lambda and s3 tests)
|
|
# so we need to pin a boto3 and botocore revision pair that we know works
|
|
boto3==1.2.4
|
|
botocore==1.3.28
|
|
six
|