Kind of self promotion to be honest so sorry to derail if so, but #18615 is adding my mypy daemon based extension for the IDLE text editor to the Popular IDE integrations section in the README, and the pull request has been sitting there since February
I think it would be essential to include #19324, as it fixes a regression introduced by #19118, which can result in really poorly formatted results for reveal_type in some cases. (So no self-promotion here, just fixing my own error...)
Is it possible to get an update on status/eta regarding 1.17? Since you opened the issue on June 17th, are any prior merge automatically included? I'm looking at #19258 in particular personally, merged the 10th.
#19425 is a regression in 1.16.1 (note that 1.16.0 is fine).
This has quite a lot of impact at day job because of big use of dmypy. A fix is ready for review in: #19428.
Would be appreciated if that can at least be fixed in 1.17.1 as the bump to a patch version that seemed okay on CI is now breaking local workflows of engineers
Activity
hauntsaninja commented on Jun 18, 2025
Would be great to land #19270
JukkaL commented on Jun 19, 2025
The release will likely be based on commit 8241059 from Jun 11.
hauntsaninja commented on Jun 19, 2025
Oh that's earlier than I expected. In that case maybe cherry pick #19277 since there have been some recent changes here that got reported by users
ilevkivskyi commented on Jun 21, 2025
I would like #15043 included. It (partially) fixes a long-standing issue with the daemon.
CoolCat467 commented on Jun 21, 2025
Kind of self promotion to be honest so sorry to derail if so, but #18615 is adding my mypy daemon based extension for the IDLE text editor to the Popular IDE integrations section in the README, and the pull request has been sitting there since February
tyralla commented on Jun 21, 2025
I think it would be essential to include #19324, as it fixes a regression introduced by #19118, which can result in really poorly formatted results for reveal_type in some cases. (So no self-promotion here, just fixing my own error...)
esarp commented on Jul 3, 2025
Release branch is cut with #19277 and #15043. Looking to see if we can include #18615 and #19324 as well.
https://github.com/python/mypy/tree/release-1.17
CoolCat467 commented on Jul 4, 2025
Also isn't too big, would be interested in seeing #19337 go through, fixing dmypy suggest when specifying absolute paths on Windows machines.
Chainfire commented on Jul 10, 2025
I would quite selfishly hope to see #19361 and #19353 included, both of which fix breaking issues in async support in mypyc compiled code
esarp commented on Jul 11, 2025
#19270, #19324, #19337, #19361, and #19353 have been included. #18615 hasn't landed yet, so hopefully can get that in the next release.
WIP changelog: #19427
I think major changes were already included in #19200, but would appreciate eyes for anything else noteworthy.
esarp commented on Jul 14, 2025
mypy 1.17 is now released: https://mypy-lang.blogspot.com/2025/07/mypy-117-released.html
hauntsaninja commented on Jul 16, 2025
Things to cherry pick if we make a 1.17.1:
(please feel free to edit this comment)
eliegoudout commented on Jul 16, 2025
Hello!
Is it possible to get an update on status/eta regarding 1.17? Since you opened the issue on June 17th, are any prior merge automatically included? I'm looking at #19258 in particular personally, merged the 10th.
Thanks!
brianschubert commented on Jul 16, 2025
@eliegoudout Good news, 1.17 has already been released: https://pypi.org/project/mypy/1.17.0. #19258 was indeed included
hauntsaninja commented on Jul 17, 2025
Regression with mypyc async: mypyc/mypyc#1120
DanielNoord commented on Jul 17, 2025
#19425 is a regression in 1.16.1 (note that 1.16.0 is fine).
This has quite a lot of impact at day job because of big use of dmypy. A fix is ready for review in: #19428.
Would be appreciated if that can at least be fixed in 1.17.1 as the bump to a patch version that seemed okay on CI is now breaking local workflows of engineers
CoolCat467 commented on Jul 18, 2025
#19428 got merged now
hauntsaninja commented on Jul 27, 2025
Cherry picking #19453 #19485 and #19428 to the release branch, I'll cut a 1.17.1 tomorrow
hauntsaninja commented on Jul 31, 2025
1.17.1 out now!
ilevkivskyi commented on Aug 29, 2025
I think we can close this (it is time to start thinking about 1.18 now)