-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Django #1702
Comments
I actually recommend waiting for PEP 561 and its implementation. Having incomplete stubs in typeshed (which I presume the machinalis stubs are) is worse than no stubs, as we've found out with some other packages (sqlalchemy was actually withdrawn for this reason). |
Trying to pick up the situation here but can I just check what was meant by 'I actually recommend waiting for PEP 561 and its implementation' @gvanrossum. I see that there are 3 methods of including types and not sure what was meant. Thanks. |
I'm assuming this would mean a separate Django-stubs package. |
a separate Django-stubs package
Yes.
|
OK, makes sense. We're going to try and bring about this django-stubs package. Kicking off at: |
We are closing all third-party stub requests issues without recent activity. We still welcome pull requests that add these to typeshed, although distributing the stubs with the the third-party package itself is preferable. |
Integrate https://github.com/machinalis/mypy-django into typeshed.
I am aware of #153 but until this is resolved the last stable version can be exposed by typeshed. This is what most people will use and having it is better than not having django type hints.
The text was updated successfully, but these errors were encountered: