1.14 Release Tracking Issue

[svalentin]

Time for the next release of MyPy!
I will be cutting the release branch today/tomorrow and try to release in a few weeks.

I know Jukka was working on some fixes. We can cherry pick them, and others, after the cut if needed.

[tyralla]

Hi! As support for PEP 702 will be included, can we consider #18090 for this release? (Besides covering descriptors, it helps to detect more deprecations of overloaded functions.)

[svalentin]

Hi! As support for PEP 702 will be included, can we consider #18090 for this release? (Besides covering descriptors, it helps to detect more deprecations of overloaded functions.)

We can include that as well, just please have it reviewed and merged. I sadly am not the best person to review it. I just changed the note to error for deprecated

[tyralla]

We can include that as well, just please have it reviewed and merged. I sadly am not the best person to review it. I just changed the note to error for deprecated

Okay, thanks, I'll ask around.

[svalentin]

Looks like #18090 is almost ready to land. I'll cut the release right after it's committed to avoid any cherry picks.

[cdce8p]

If the branch isn't cut yet, maybe we could also get one more typeshed sync just to pull in the latest changes? Opened #18248.

[svalentin]

Sorry for the delay! We spent some time testing Dropbox's codebase on the new potential mypy commit base, and that dragged on.
I'll have to make the release cut at commit 5082a22 since that's what we ended up testing in Dropbox. I'll cherry-pick #18090 since it's related to a feature we already include in the release and also disabled by default.
I've chatted with @JukkaL and sadly won't cherypick the typeshed syncs that followed, like #18248 since we need to test it.
Release branch: https://github.com/python/mypy/tree/release-1.14

[JukkaL]

If there is some specific typeshed commit that somebody would like to cherry-pick, that may be still feasible. I'm looking at one potential minor typeshed regression myself, but I'm not sure if I have time to investigate it before the release is out.

[svalentin]

This PR updates the changelog for the release - #18301
Please leave a comment if you would like to change anything.

[bew]

Hello o/
When do you think the release will land? next few days? weeks?

In nixpkgs the mypy pkg is currently disabled for py3.13 (and is still at mypy1.11), which is preventing use of many nix packages in py3.13 since many depend on mypy for testing.

I saw that 1.13 is starting to have py3.13 support so I was thinking about upgrading the mypy pkg to 1.13 but if the 1.14 is very-soon-to-be-released I'll just wait for the release and upgrade 1.11 -> 1.14 in one go.

What do you think?

[svalentin]

I hope to release it in the next few days! We're in the final stages of the release, writing the changelog.

[svalentin]

Mypy 1.14 is out now! Read the blog post here: https://mypy-lang.blogspot.com/2024/12/mypy-114-released.html

[JelleZijlstra]

#18320 is a regression that looks relatively bad. #18324 is a fix

#18322 is a minor regression that affected typeshed

[hauntsaninja]

#18350 fixes a mypyc regression

[hauntsaninja]

#18379 fixes a regression

[svalentin]

I'll start the point relese for the regression fixes

[svalentin]

I'll cherry pick these:

• 55d4c17 - Revert "Remove redundant inheritances from Iterator in builtins" (Revert "Remove redundant inheritances from Iterator in builtins" #18324)
• e139a0d - Fix enum truthiness for StrEnum (Fix enum truthiness for StrEnum #18379)
• d79d89e - Fix getargs argument passing (Fix getargs argument passing #18350)

[svalentin]

Mypy 1.14.1 is out now with the 3 fixes mentioned above!