-
Notifications
You must be signed in to change notification settings - Fork 437
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
Add empty stubs for Django __init__ files #321
Conversation
4b2ca44
to
ba87516
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.
@gbleaney has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
While Pyre seems to handle the absence of `__init__.pyi` well, there can be problems with other type checkers that use its Django stubs. Adding these stub files makes the others discoverable, much like adding empty `__init__.py` files to Python packages.
ba87516
to
2dbe9a3
Compare
@dirn has updated the pull request. You must reimport the pull request before landing. |
@gbleaney I rebased this on top of the latest version of |
This is a work-in-progress attempt at switching over to mypy as part of #85. At the moment everything seems to be working except for the some changes to pyre's stubs that are addressed in facebook/pyre-check#321.
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.
@gbleaney has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
Sorry for losing track of this @dirn! I've re-imported and will try to land today |
While Pyre seems to handle the absence of
__init__.pyi
well, there canbe problems with other type checkers that use its Django stubs. Adding
these stub files makes the others discoverable, much like adding empty
__init__.py
files to Python packages.