make dependency on logging less restrictive in error_reporting#5345
Conversation
|
@theacodes ISTM that with logging at > 1.0, we could amend the logging pin to |
|
Yeah go for that. I seem to remember us wanting to just absorb error reporting into logging. |
|
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
|
This has already been merged, but just for completeness: I hereby to confirm that I am happy for this altered commit to be merged. Would be fantastic to see a new version being pushed to PyPI :-). |
This PR makes the dependency on
google-cloud-pythonless restrictive ingoogle-cloud-error-reporting. Currently, it is not possible to installgoogle-cloud-error-reportingalongside other up-to-dategoogle-cloud-pythonpackages.Of course, there may be great reasons why it was so restrictive in the first place, in which case I'd love for the author to explain the cause.
If this change is fine, it would be great if this was merged swiftly and published to PyPI with an updated version number.