-
Notifications
You must be signed in to change notification settings - Fork 207
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
process: add mypy session for samples #551
Conversation
Hm... this will likely not be mergeable, because |
c80c04e
to
5fe8d2b
Compare
5fe8d2b
to
232e7d4
Compare
232e7d4
to
0fdbfdf
Compare
0fdbfdf
to
be7a0cd
Compare
1d18db7
to
d57ab44
Compare
d57ab44
to
9b86464
Compare
9b86464
to
b82f149
Compare
The version pins that require recent enough depndencies for the sake of static type analysis should be placed in the corresponding nox session definition. They should not interfere with dependency versions used for testing the code at runtime, i.e. when running the tests.
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.
LGTM except for a couple of nits.
Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot. |
Towards #536.
This PR adds the
mypy
session for samples and cleans up their type annotations.However, the PR does not address the errors caused by
mypy
not realizing that a lot of methods from the generated client are dynamically injected into the hand written class. It also does not deal with a few missing annotations ingoogle-api-core
(e.g.retry.Retry
).Additional thing to consider is that the client classes that the end users use now have many more methods on them that were previously stored on their
client.api
attribute (and the .api
attribute has been removed). Caution is needed here.