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
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.
@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?
@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.
@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 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.
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?
Activity
koogoro commentedon Aug 22, 2023
I've run into a regression: #15932.
tyralla commentedon Aug 22, 2023
If this is the right place to bring attention to old, so far undiscussed pull requests: #14440
AlexWaygood commentedon Aug 27, 2023
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 commentedon Aug 28, 2023
@koogoro I have a suggestion on the blog post: Could you please mention there that
--new-type-infernecewill be on by default in 1.7?koogoro commentedon Aug 29, 2023
The branch has been created. The new functionality in the
attrsplugin to coverfieldsmight cause some errors to pop up for users ofattrsbut 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 commentedon Aug 29, 2023
@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 commentedon Aug 29, 2023
@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 commentedon Aug 29, 2023
@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 commentedon Aug 29, 2023
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 commentedon Aug 29, 2023
I did find one regression in d7b2451: #15984. This regression's new in between that and the current release point, maybe due to some
ParamSpecchange between the two?hauntsaninja commentedon Aug 31, 2023
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 commentedon Sep 1, 2023
We should cherrypick #16013 in case we don't have a release before Python 3.12 is out
koogoro commentedon Sep 2, 2023
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.
13 remaining items
JukkaL commentedon Oct 10, 2023
Cherry-picked these PRs to the release branch:
JukkaL commentedon Oct 10, 2023
And the release is out: https://mypy-lang.blogspot.com/2023/10/mypy-16-released.html
JukkaL commentedon Oct 10, 2023
I will update the website tomorrow, since it's getting late here.
AlexWaygood commentedon Oct 11, 2023
A new crash with mypy 1.6, that I hit when trying to bump typeshed's mypy pin:
intgr commentedon Oct 11, 2023
@ymyzk Can you please add mypy 1.6.0 to mypy-play.net?
ymyzk commentedon Oct 11, 2023
@intgr Yes, thanks for the reminder. I added mypy 1.6.0 and updated mypy-play.net ymyzk/mypy-playground#488
intgr commentedon Oct 11, 2023
I experienced two regressions with mypy 1.6.0, both involving
ParamSpec:strict-optionalforget None'able argument (with ParamSpec decorator) #16246ParamSpec[Concatenate[]]is not compatible withCallable[..., Any]#16247ilevkivskyi commentedon Oct 12, 2023
An obvious candidate for 1.6.1 #16251 (fixes two closely related crash regressions).
AlexWaygood commentedon Oct 13, 2023
Another new crash in mypy 1.6 (that still reproduces with mypy
masterand the latest version of therelease-1.6branch):typing.ParamSpec#16257AlexWaygood commentedon Oct 13, 2023
#16258 fixes a regression of sorts, so might be worth including in a patch release? But the regression was a new in mypy 1.5 rather than mypy 1.6.
ilevkivskyi commentedon Oct 13, 2023
Also CP for 1.6.1 #16259
intgr commentedon Oct 17, 2023
FYI mypy website https://mypy-lang.org/ does not display the 1.6 release in "What's new"
hauntsaninja commentedon Oct 17, 2023
I cherrypicked these to release-1.6 branch and will cut the release later today:
hauntsaninja commentedon Oct 18, 2023
https://pypi.org/project/mypy/1.6.1/ is now a thing
I also left some notes at https://github.com/python/mypy/wiki/Release-Process#making-a-patch-release so I don't have to grep through my shell history next time to see if I forgot something