Skip to content

Fix mypy type annotations #1696

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

Merged
merged 6 commits into from
May 7, 2020
Merged

Fix mypy type annotations #1696

merged 6 commits into from
May 7, 2020

Conversation

fmassa
Copy link
Member

@fmassa fmassa commented Dec 20, 2019

Looks like we need to specify return annotations to be compliant with mypy.

@fmassa fmassa requested a review from eellison December 20, 2019 15:30
Copy link
Contributor

@eellison eellison left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - thanks for doing this! kind of annoying that we have to but oh well

@zhangguanheng66 zhangguanheng66 force-pushed the fix-mypy branch 3 times, most recently from bfcf96c to 062b874 Compare May 6, 2020 19:31
@fmassa
Copy link
Member Author

fmassa commented May 7, 2020

Awesome, thanks a lot for finishing it @zhangguanheng66 !

@fmassa fmassa merged commit f71316f into pytorch:master May 7, 2020
@fmassa fmassa deleted the fix-mypy branch May 7, 2020 17:37
fmassa added a commit to fmassa/vision-1 that referenced this pull request Jun 9, 2020
* Fix mypy type annotations

* follow torchscript Tuple type

* redefine torch_choice output type

* change the type in cached_grid_anchors

* minor bug

Co-authored-by: Guanheng Zhang <[email protected]>
Co-authored-by: Guanheng Zhang <[email protected]>
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.

2 participants