1.16 Release Planning

[jhance]

I am planning to release 1.16 in the coming weeks.

If there are any PRs you would like to ensure are included, please mention here.

This issue will be updated once the release branch is cut.

[hauntsaninja]

Note there's a crash on mypy master we may want to address #18764

Update: fixed by Ivan

[ilevkivskyi]

FWIW worth including two low-risk crash fixes in the release:

• Fix crash on type inference against non-normal callables #18858
• Fix crash on multiple unpacks in a bare type application #18857

[cdce8p]

What's the current status here? Has the release branch been cut already?

If not, I'd suggest to do it after the current typeshed sync #18880. This is the last commit with support for type checking Python 3.8. For the next typeshed sync, we'll need to drop support for --python-version 3.8 completely. Might be great to get one last release out before that.

[svalentin]

If possible, we should include #18906 in the new release. It fixes high pri daemon bug

[jorenham]

If not, I'd suggest to do it after the current typeshed sync #18880. This is the last commit with support for type checking Python 3.8. For the next typeshed sync, we'll need to drop support for --python-version 3.8 completely. Might be great to get one last release out before that.

Why not just drop 3.8? It has been EOL for over 6 months now

[cdce8p]

Why not just drop 3.8? It has been EOL for over 6 months now

We already dropped 3.8. It's just that mypy still supports checking 3.8 code with --python-version 3.8 for now. This will become impossible with the next typeshed update #18930.

[jorenham]

Hmm that's too bad. Because #18930 contains ctypes improvements (python/typeshed#13777 and python/typeshed#13760) that matter to numpy.

[cdce8p]

Hmm that's too bad. Because #18930 contains ctypes improvements (python/typeshed#13777 and python/typeshed#13760) that matter to numpy.

I'd be fine with dropping it now as well. The idea just was to do one last release before then. The release branch could have even been cut already. I just don't know.

[meshy]

Will it be possible to have #15043 in 1.16? If not, can I please ask for some feedback on the issue as to what else is required before it's merged?

[jorenham]

For NumPy #18997 is a big problem. We won't be able to release numpy/numtype (a rework of numpy's typing stubs with new (backwards-incompatible) features like shape-typing).

The plan is to publish an the initial NumType release in one or two months. So if this isn't fixed in mypy 1.16, our only option would be to drop support for mypy. I really don't want that.

[ilevkivskyi]

@meshy There was a recent change that likely will make ancestors included in seen modules, so I think your PR can likely be simplified. That said however, realistically I think it likely won't make it into 1.16, but I promise I will get back to it as soon as I am done with other 1.16-related work (I was bothered by this issue myself, so I am interested in it being fixed).

@jorenham I strongly suggest you drop this "or otherwise" attitude. If you think it will persuade someone, then I can tell you it will be the opposite.

[jorenham]

I strongly suggest you drop this "or otherwise" attitude. If you think it will persuade someone, then I can tell you it will be the opposite.

Oh woops I see how it can be interpreted that way, and I did not mean it as a threat or something. I was just trying to say that I consider it to be very important that we keep on supporting mypy, and that I'm therefore willing to help in any way I can in solving this issue.