-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Mypy 1.4 Release Planning #15372
Comments
I hope you mean the 1.4 release :) |
Update: Fixed with #15383 The mypy wheel build seems to be broken atm. It seems to be platform specific to Cross posting it here to keep track. |
Updated the version number. |
Hmm, I'm not sure how that happened. I suspect I copied the issue template from the oldest link in our table, rather than the newest one, and then incremented that without thinking if the version number made sense. |
|
Also, just to note: #15161 caused a LiteralString-related regression for typeshed that still exists on the master branch. I reported the regression here immediately after the PR was merged: #15161 (comment). It looks like it's probably a typeshed-specific problem, and we can definitely just work around it in typeshed if we need to. So it's not a huge issue by any means. Just thought I'd mention it anyway, though! |
I am going to work on some recently reported crashes. I will post them here as soon as I have a fix, the first will be #15351 |
And here is a fix for this crash #15402 |
And here is a fix for another crash #15403 |
And yet another crash fix #15404 |
And here is yet another crash fix #15407 |
Would love to see #15413 included. That change alone removes 23 unnecessary |
I think these two batches are good candidates for cherry-picking:
|
Oh and one more things, it seems these error codes do not have documentation (at least neither my script nor me have found it): known_missing = {
# TODO: fix these before next release
"annotation-unchecked",
"empty-body",
"possibly-undefined",
"str-format",
"top-level-await",
} |
@ymyzk Can you please add mypy 1.4.0 to mypy-play.net? |
@intgr It should be available on mypy Playground now: ymyzk/mypy-playground#388 |
Wait, so this is already released? Is it early July already? What was the point of not including the stable error code links in the release? |
This was the postponed May mypy release. I think stable error code links arrived too late in the release process, but there will be a 1.5 release in July (targeting early July). @svalentin is the RM for 1.5. |
In case there is a
Fix for |
You'll probably also want to cherry-pick this, if there is a 1.4.1 release -- our test suite was very broken by the pytest release earlier today: |
I've cherry picked the following to the 1.4 release branch: Fix for async type checking regression
A fix for typeshed (reverts a PR that fixed another problem that only manifested on typeshed)
Docs changes:
Fixes for CI and wheel build:
Hopefully this is all good. If I don't hear anything, I'll make a patch release this weekend (really excited to have the 1.4 speedups at work, but the async thing is a blocker) |
I've released mypy 1.4.1 |
Was #15429 actually included in 1.4.1 ? I still have the issue where
|
I don't see it in https://github.com/python/mypy/commits/release-1.4 |
The mypy website https://www.mypy-lang.org/ still hasn't been updated to list version 1.4. |
I'm planning to make a 1.4 release around early July. (This is actually meant to be the June release but it is delayed).
Please post here any issues you'd like to see fixed in the release, or PRs you'd like to have merged. The release branch is available as release-1.4.
The text was updated successfully, but these errors were encountered: