-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Added type annotations to pip._internal.commands.check #7977
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
Conversation
77f4473
to
ed3561e
Compare
ed3561e
to
21b5357
Compare
21b5357
to
e50efcd
Compare
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, minus one annotation that needs to be changed.
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.
This still needs changes.
Could you specify where in the code do I need to change :) I will update accordingly |
@deveshks We'd want to fix the annotation in upstream typeshed, and then come back to this PR once there's a new mypy release w/ an updated typeshed. Until then, I don't think we should add a misleading type annotation to our codebase. :) |
e50efcd
to
3c4452f
Compare
Hi @pradyunsg As per your suggestion, I have reverted the type annotations added to |
3c4452f
to
c2fdf4a
Compare
Hi @pradyunsg If there are no more concerns with this PR, could I get it approved/merged 😊 I will keep future PR related to mypy annotations at one file per PR, as per your comment at #4748 (comment) . It does make it easier to get reviewed. |
Towards #4748
Added type annotations to
pip._internal.commands.check