You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to release mypy 0.620 on Tuesday July 10. The release branch is going to be cut on Thursday July 5. Please mention here any PRs that you would like to include in the release.
I'd like to land my PR for partially overlapping types -- I should have some free time tomorrow I can use to work on this.
I'm also planning on polishing up #5296 later tonight + submitting one or two additional PRs tomorrow for improving overload error messages and other small quality-of-life usability improvements sometime tomorrow. That said, I don't think it's super crucial for those PRs to be included in the upcoming release.
Two candidates for cherry picking are #5336 and #5338 (the latter crash is clearly a regression, while the first one is not a regression with the repro I found, it could be triggered by other code paths since we are doing more things with overloads now).
Activity
Michael0x2a commentedon Jul 4, 2018
I'd like to land my PR for partially overlapping types -- I should have some free time tomorrow I can use to work on this.
I'm also planning on polishing up #5296 later tonight + submitting one or two additional PRs tomorrow for improving overload error messages and other small quality-of-life usability improvements sometime tomorrow. That said, I don't think it's super crucial for those PRs to be included in the upcoming release.
emmatyping commentedon Jul 4, 2018
I think it would be nice to get #5303 in, since it will avoid some potential pain with working with PEP 561 packages.This was merged.emmatyping commentedon Jul 8, 2018
#5331 is a regression on 0.610, so we should probably fix it before release.This is fixed in #5332.ilevkivskyi commentedon Jul 8, 2018
The release branch is now cut https://github.com/python/mypy/tree/release-0.620 and most important fixes are in.
ilevkivskyi commentedon Jul 9, 2018
Two candidates for cherry picking are #5336 and #5338 (the latter crash is clearly a regression, while the first one is not a regression with the repro I found, it could be triggered by other code paths since we are doing more things with overloads now).
ilevkivskyi commentedon Jul 10, 2018
I think I will postpone the release for tomorrow. I will cherry-pick the fixes, and wait for another day.
ilevkivskyi commentedon Jul 13, 2018
The version 0.620 is now released!