-
Notifications
You must be signed in to change notification settings - Fork 599
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
Support PyMySQL 1.x series #792
Conversation
d7ec723
to
8ea7c3e
Compare
8ea7c3e
to
3498e8f
Compare
@@ -462,7 +462,7 @@ deps = | |||
psycopg2 ~= 2.8.4 | |||
aiopg >= 0.13.0, < 1.3.0 | |||
sqlalchemy ~= 1.4 | |||
redis ~= 3.3.11 | |||
redis ~= 3.5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
celery tests are failing with redis 3.3 so had to upgrade
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
curious , why did celery tests fail with redis 3.3?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We pinned redis but did not pin celery. Latest version of celery/kombu passes extra params to redis which 3.3.x did not accept.
@@ -462,7 +462,7 @@ deps = | |||
psycopg2 ~= 2.8.4 | |||
aiopg >= 0.13.0, < 1.3.0 | |||
sqlalchemy ~= 1.4 | |||
redis ~= 3.3.11 | |||
redis ~= 3.5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
curious , why did celery tests fail with redis 3.3?
Description
Fixes #791
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Does This PR Require a Core Repo Change?
Checklist:
See contributing.md for styleguide, changelog guidelines, and more.