-
Notifications
You must be signed in to change notification settings - Fork 371
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
Considered using PEP-484 type annotations? #248
Comments
Thanks for asking! I can't remember offhand whether there are existing plans for backporting that feature to Python 2. My default instinct is to avoid Python 3 specific things (even in an optional mode) because they generally don't add enough benefit to be worth the expected support burden (i.e. confused users trying to use those features on Python 2; extra code divergence between the interpreters; etc). So, I'm neutral on the overall idea but it hinges on that question. Let me know if you look into that. |
At least mypy (where PEP-484 originates from) lists python 2.x support for 2015 in their roadmap: http://mypy-lang.org/roadmap.html |
Linking this to #357 which is semi related (it's re: folks using this functionality in Python 3, for its own sake, not re: any internal support). |
hi! are there plans for https://github.com/python/mypy support? |
They will be the standard way to type annotate function signatures (including parameterized types like lists, dicts, etc.), and are run-time accessible. Is it worth looking into using that?
The text was updated successfully, but these errors were encountered: