-
Notifications
You must be signed in to change notification settings - Fork 24
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
State of the project #9
Comments
Great project! Do you need any help with it? |
Any news? |
Any updates on a project? |
OK, it's been a year now ... for the ones who already commented, here's a proposal:
How does it sound? I can do this if we're in agreement 👍 👍 👍 |
There was some effort in python/typeshed#1702 to talk about plans. Is https://www.python.org/dev/peps/pep-0561/ usable now? Can we do that? |
@lwm I have some very-very dirty implementation of Please, invite me to collaborate! |
@sobolevn, I've invited you to collaborate on https://github.com/lwm/mypy-django! https://github.com/lwm/mypy-django#this-is-a-friendly-fork Come one, come all! |
Update: we're moving along at https://github.com/TypedDjango/django-stubs#django-stubs now! |
Hi, @dmoisset!
I really like the initiative taken by you and your collegues over at Machinalis. Static type checking for Django on a general basis would be great!
For the moment it is really difficult to investigate the state of static type checking in the Django community. When searching around I have found this repository and several Google usergroup threads heavily involving you, but more recent information is hard to come by.
Is it possible to adress this in the README in this repository? Questions I have are:
python/typeshed
repository?Thanks,
Jakob
The text was updated successfully, but these errors were encountered: