-
Notifications
You must be signed in to change notification settings - Fork 641
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
Require aiopg to be less than 1.3.0 #560
Require aiopg to be less than 1.3.0 #560
Conversation
@@ -13,4 +13,4 @@ | |||
# limitations under the License. | |||
|
|||
|
|||
_instruments = ("aiopg >= 0.13.0",) | |||
_instruments = ("aiopg <= 1.2.1",) |
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.
shouldn't this be >=0.13.0, <1.3.0
consider 1.3 introduced the breaking change and for some reason we did not want to support versions older than 0.13?
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.
I wasn't aware of the support of multiple conditions in python.
I have updated accordingly.
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.
Thanks. Can you please open an issue that tracks adding support for 1.3.0 and newer versions? Please also include details about the issue this instrumentation has today.
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.
Created as #561
For more context, breaking change introduced here: https://github.com/aio-libs/aiopg/pull/813/files |
Description
Aiopg latest version has breaking changes in its internal object.
It breaks the build in default branch.
I have fixed the version here to make the build pass first.
It has a break changes in its API so we may need a further discussion on how to handle this case.
Fixes # (issue)
Type of change
How Has This Been Tested?
Does This PR Require a Core Repo Change?
Checklist: