-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Support new Python 3.5 features #913
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
Comments
Also #706 (async and await) |
In every Python release there are also a bunch of stub changes. |
I'm going to focus on Python 2 and better pre-3.5 Python 3 support first, so taking away the priority tag. The rationale is that way more people are using older Python releases and they still aren't well supported by mypy. PRs that add new Python 3.5 features are still welcome, though. |
Hi @JukkaL How much time would it take you to resolve the following issue with 3.5 compatibility:
It seems that it is not compatible with the standard I'm using Python 3.5 in production, btw. |
I think a new release would fix this. @avanov I believe this already works in master. |
Yeah, we need to cut a new release to get at least minimal Python 3.5 compatibility. @avanov Let me know if using github master works for you. A lot has happened since the last release so preparing release notes is going to be some work. Also there are a few major bugs that I'd like to fix before the release. |
@kirbyfan64, @JukkaL thanks for the tip, |
And there's something wrong with
|
@JukkaL I totally understand the decision to support 2 before 3.5, but one counterpoint to bring into the discussion would be the folks who are willing to adopt 3.5 are also likely to be the folks who are willing to adopt types. I was pretty bummed to learn I'll have to choose between types and async/await for now. I think 3.5 will be a banner release for Python 3. The combination of type hinting and async/await made me choose it for my latest project, and I know a lot of other developers are excited about this release for that same reason. It'd be amazing if these two worked well together with Mypy and we could start developing awesome examples of modern Python. |
@avanov Could you file a separate issue for that crash, and maybe try to come up with a short code sample that reproduces the crash? The latest github master should provide more information in the traceback. @rowillia I know -- it's a hard decision. I probably won't have any spare bandwidth in the next several weeks, but I might look at 3.5 support (at least async/await) in early 2016. If somebody sends a PR I'll do my best to review it pretty quickly. |
@JukkaL I'll do later this week. Thanks for the feedback! |
@JukkaL Do you guys have any docs for your Python 2 plans? Are you going to backport PEP 3107? It'd be great if this used the same format as PyCharm https://www.jetbrains.com/pycharm/help/type-hinting-in-pycharm.html#d302201e159 since they've already got some tooling around supporting it. EDIT: Sorry @gvanrossum, I'll leave this for 3.5 features. If I have some time I'll look into implementing async/await support. |
We're not planning to backport function annotations to Python 2.7.
Once we're happy with how this works out we will document it. (Please, if you have more questions about this topic, open a new issue -- this issue should really be reserved for new 3.5 features such as |
IMO main thing is async def and friends (PEP 492). See python/typing#119 |
Closing in favor of a more specific task, #1453. |
Python 3.5 has a bunch of new things mypy doesn't quite support yet:
https://docs.python.org/3/whatsnew/3.5.html
This is an umbrella task for all Python 3.5 related issues (except for PEP 484 related tasks).
The text was updated successfully, but these errors were encountered: