-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Release 0.590 planning #4839
Comments
I'd like to include turning incremental mode on by default in this release (#4841 is a rerequisite). [done] |
And that in turn depends on #4840. [done]
|
Also just a wish: it would be great if PEP 561 support and related PRs would be included in the release. [done] |
I also wish to make PEP 561 support a priority for this external release.
|
Agreed that PEP 561 support would be great. I'll do a full review iteration tomorrow. Hopefully we can get the PR merged this week (even if there is some remaining non-essential follow-up work). @ethanhs Do you have time to continue updating #4693 this week? If yes, we can schedule my code review(s) so that you have time to respond before the release branch is cut on Monday. |
@JukkaL yes, I will have time this week. I too am keen to get it merged soon! |
OK, I've cut the release branch: https://github.com/python/mypy/tree/release-0.590
Namespaces (#4277) did not make it in. |
Critical bug to fix:
(We're now on a branch for typeshed too, and only required fixes will be cherry-picked there.) |
If there's anything that desperately should go into release-0.590, speak now! |
|
Any chance to include python/typeshed#2034 ( |
No, the release is going to be in ~5 hours. It will likely make it in the next release in several weeks. |
The current plan is to release mypy 0.590 on Friday, April 13. The release branch will be cut on Monday, April 9.
The text was updated successfully, but these errors were encountered: