Release 0.720 planning

[ilevkivskyi]

I plan to release mypy 0.720 on Friday July 12. The release branch will be cut in one week, on Tuesday July 9.

This will be the first release where the new semantic analyzer will be used by default. The old one will be still available with --no-new-semantic-analyzer but will be likely removed in 0.730.

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.

[Michael0x2a]

Oh wow, that was quick -- exciting!

There are a few enums and literal types related PRs I think would be nice to get merged -- namely:

• 7000: Generalize reachability checks to support enums
• 6560: Support method plugin hooks on unions
• 6558: Add union math for intelligent indexing

But these PRs have been deferred for several releases, so I think it's no big deal if we defer them for another one.

This is also a heads-up that I'll be submitting a few more reachability related PRs later this week. One of those PRs will be adding docs for the --warn-unreachable flag: I'd like to get that one landed before the release. The other PRs will be less important, I think.

[brandtbucher]

Typo in the issue title?

[ilevkivskyi]

Typo in the issue title?

Oh indeed :-) Will fix now.

[ilevkivskyi]

There are a few enums and literal types related PRs I think would be nice to get merged -- namely:

Hm, interesting, I was thinking about exactly the same bunch of issues. I will try to land them by the end of the week.

[awelzel]

@ilevkivskyi - mind checking out #7108? We're heavily using namespace packages and are running into #5854.

[ilevkivskyi]

Someone else will need to review it, @gvanrossum will you have time for this?

[ilevkivskyi]

I think #7044 is currently a release blocker.

[Deimos]

@ilevkivskyi just to confirm (I created #7044) - my codebase no longer crashes with the new semantic analyzer after that fix, but it does output a number of errors that aren't actually errors. I haven't looked through them all yet, but they seem to mostly be related to either @property or SQLAlchemy @hybrid_property, including the issue I commented about here with a discrepancy in getter/setter types.

[ilevkivskyi]

Release branch is cut: https://github.com/python/mypy/tree/release-0.720

[ilevkivskyi]

@Deimos I believe most of those errors can be fixed by something like (didn't try this):

if TYPE_CHECKING:
    from builtins import property as hybrid_property
else:
    from sqlalchemy.ext.hybrid import hybrid_property

[Deimos]

That seems to work, yes. That seems like a reasonable workaround to use, thanks!

[JelleZijlstra]

In our codebase there seems to be a regression on current master where functions decorated with https://github.com/quora/qcore/blob/master/qcore/caching.pyi#L79 degenerate to Any. I'll have some time later today to investigate more and try to find a minimal repro.