-
Notifications
You must be signed in to change notification settings - Fork 1
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
Where to take this project: direction, thoughts, proposals #1
Comments
Here's some discussions from the Django development mailing list:
Oh, right, it seems someone has already started to do this: However, I then saw this:
It seems others were waiting for PEP 561 as well. I'll create a new mail on the development list and see what kind of traction it gets. |
Just fired a mail at https://groups.google.com/forum/#!forum/django-developers.
EDIT: https://groups.google.com/forum/#!topic/django-developers/xB3kla9RJbo |
Closing off, things have come along, we're focusing work over at: |
Following the recommendation in python/typeshed#1702 (comment) of:
I think we need to orientate the development of this repository specifically around how PEP 561 will work and whatever work flow is necessary to support that integration.
There are some notes around this on the
mypy
documentation:I see no existing ticket regarding adding type hints on the Django tracker:
It probably makes sense to drop a mail on the dev list to see where we can coordinate.
Open to any thoughts!
I can put an hour or two each week and use Django in my day to day work, so I would definitely like to have access to the type hint system going forward. It's also a way to give back to the Django community which really has got me a long way so far ...
The text was updated successfully, but these errors were encountered: