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

Fix overstrict protobuf pin #132

Merged
merged 1 commit into from
Oct 21, 2022

Conversation

threewordphrase
Copy link
Contributor

@threewordphrase threewordphrase commented Oct 18, 2022

The fix merged in #126, pinning protobuf==3.20.1 conflicts with (at least) google-api-core's recent pin on !=3.20.1.

The original issue, #125 , appears to only be an issue with protobuf>=4.21.0. This PR goes back to the old > pin with an additional constraint on <4.21.0. This should address the original issue without being unnecessarily restrictive and causing conflicts with other packages.

Exact pinning by pip packages is problematic and discouraged. In this case, it breaks our pip-compile workflows as no acceptable version of protobuf can be found.

@threewordphrase threewordphrase changed the title Fix overstrict pin Fix overstrict protobuf pin Oct 18, 2022
@threewordphrase
Copy link
Contributor Author

@emaderer tagging because you merged #126 in, could you take a look at this? Thank you!

@emaderer emaderer merged commit cb8b005 into signalfx:master Oct 21, 2022
@threewordphrase
Copy link
Contributor Author

@emaderer thank you! Do you know when this will land on pypi?

@rmfitzpatrick
Copy link
Contributor

@threewordphrase thanks for the update and your patience. Published https://pypi.org/project/signalfx/1.1.16/

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.

None yet

5 participants