Mypy 1.6 Release Planning

[koogoro]

I'm planning to make the 1.6 release by the end of August.

Please post any issues you'd like to see fixed in the release here, or any PRs you'd like to have merged. I'll make the release branch release-1.6.

[koogoro]

I've run into a regression: #15932.

[tyralla]

If this is the right place to bring attention to old, so far undiscussed pull requests: #14440

[AlexWaygood]

It would be good to get #15960 (or an equivalent fix) in before the release. It fixes some recent stubtest regressions that I introduced.

(EDIT: Now merged! :)

[ilevkivskyi]

@koogoro I have a suggestion on the blog post: Could you please mention there that --new-type-infernece will be on by default in 1.7?

[koogoro]

The branch has been created. The new functionality in the attrs plugin to cover fields might cause some errors to pop up for users of attrs but this isn't really a regression and I don't think the primer noticed anything, so I've marked this as a feature request: #15980.

[koogoro]

@AlexWaygood That commit didn't make it onto the branch, and it also doesn't cherry-pick cleanly. Does that mean that the change that introduced the issue didn't make it onto the branch, or would it be good to include multiple more commits on the release branch?

[cdce8p]

@koogoro Thanks for creating the release branch. I noticed that it branched of over a week ago. Was that intentional? It's missing a lot of the recent PRs especially from @ilevkivskyi. If you're not too far along with testing it, might I suggest hard reseting the branch to the current master commit? 010da0b That would also include the stubtest fix @AlexWaygood mentioned.

https://github.com/python/mypy/commits/master
https://github.com/python/mypy/commits/release-1.6

[koogoro]

@cdce8p The wheels build failed for the latest commit, so I'll use the one before it, d7b2451. Let me quickly check if there are any large problems before hard resetting it.

[AlexWaygood]

@AlexWaygood That commit didn't make it onto the branch, and it also doesn't cherry-pick cleanly. Does that mean that the change that introduced the issue didn't make it onto the branch, or would it be good to include multiple more commits on the release branch?

I was hoping 0b303b5 would make it into the release, and if it does, it's important d7b2451 does also, as it fixes some regressions introduced by 0b303b5. But if neither commit makes it in, that's also okay, it can wait :)

It would be pretty useful if 48835a3 could be included in the release, though — this one fixes a crash that's blocking some typeshed updates.

[koogoro]

I did find one regression in d7b2451: #15984. This regression's new in between that and the current release point, maybe due to some ParamSpec change between the two?

[hauntsaninja]

It would be good to cherrypick #16004 (fix for #14740 which was highly requested config option). You may also need #15992 for CI to work

[hauntsaninja]

We should cherrypick #16013 in case we don't have a release before Python 3.12 is out

[koogoro]

Cherry-picked 0ae0c75 as a fix for #15984 and 379b52f as a fix for #15990. I'll cherry-pick #16004 and #16013 once they've been merged.