Release 0.790 planning

[JukkaL]

I plan to release mypy 0.790 around Aug 25 and cut the release branch this Thu (Aug 13).

Please add comments to this issue if you have any PR you'd like to be included. Ideally those PRs should be landed before the release branch is cut, to minimize cherry-picking.

(This will hopefully be the final major release with bundled monolithic typeshed. 0.800 should have third-party package stubs available from PyPI.)

[JukkaL]

I'm encountering what looks like a hard crash (no traceback) on Linux with Python 3.6 when running the latest master against Dropbox internal code.

It started happening after 88eb84e was merged. Looking at that PR, I don't see anything particularly suspicious, but it's doing some pointer casting which might plausibly be a problem. If I can't fix the crash soon, I might cut the release branch from an earlier commit or wait a bit longer until I cut the release branch.

[JukkaL]

I narrowed down the segfault to mypyc/mypyc#756. It's a release-blocker, unless we cut the release branch from an earlier commit and do some cherry-picks.

[msullivan]

Is the branch cut happening today? I've been seeing infinite loops with --follow-imports=normal on https://github.com/edgedb/ and will try to investigate and get a PR up today.

[TH3CHARLie]

Is the branch cut happening today? I've been seeing infinite loops with --follow-imports=normal on https://github.com/edgedb/ and will try to investigate and get a PR up today.

I think it will happen today since the fix for mypyc/mypyc#756 would be then included and no cherry-picking is needed.

[msullivan]

I'd like #9302 to make it into the release

[hauntsaninja]

I'm late to the party, but it'd be nice if this typeshed sync #9317 containing python/typeshed#4447 made it in

[TH3CHARLie]

I'm late to the party, but it'd be nice if this typeshed sync #9317 containing python/typeshed#4447 made it in

according to the branches page, the release 0.790 branch was already cut last Friday.

[JukkaL]

The release will be delayed by at least a few days, since I didn't manage to update Dropbox internal mypy version to the release branch last week, and this week I'm on vacation. I want at least 3 days of internal testing at Dropbox before a release.

@hauntsaninja I'll need to make some other typeshed fixes as well before the release, so there should be no problems including your fix as well.

[msullivan]

Any updates on release schedule?

[gvanrossum]

I imagine the internal testing might have been prolonged due to the flurry of typeshed changes due to some folks at Microsoft submitting a truckload of new packages and tightening many existing packages.

[JukkaL]

Yeah, the release is delayed because of the various typeshed changes that either require fixes in typeshed or fixes to our internal codebases. Also some of them exposed mypy bugs that we may want to fix before the release.

I already used all the time I had reserved for preparing for the release, so I'll have to scramble a few hours here and there to finish the release, unfortunately. (But I want to get it out ASAP.)

I'll post an update once we've started testing the release branch internally.

[emmatyping]

Since Python 3.5 is going to be sunsetting in 11 days, may I recommend we make this the last release to support running mypy with Python 3.5 as well?