Release mypy 0.520

[JukkaL]

Tentative timeline:

• Friday July 7 2017 08:00 UTC: Feature freeze starts
• Monday July 10 2017 around 20:00 UTC: Release out

If you have any open PRs that you'd like to see included, leave a comment here and we'll see if it's possible. New features probably have to be merged on Thursday at the latest. Documentation updates and high-priority, low-risk bug fixes can also land after Thursday, but merging any PRs from Friday morning (UTC) until the time of the release is subject to approval from me.

[JelleZijlstra]

I think we should fix python/typeshed#1464, since it's a regression since the most recent mypy release.

[ilevkivskyi]

I would prefer #3524 to be merged. It fixes two (and half) issues (one of which is a relatively old high-priority issue). If it is merged, then I can quickly add the docs mentioned in #3494.

[emmatyping]

I think Im interested in solving python/typeshed#1175, so I will get on that now. I might also work on python/typeshed#1446 .

[Michael0x2a]

It'd be cool if #3665 could be merged, but I'm sure everybody's busy and the change is mainly an ergonomic one so I wouldn't mind if it was de-prioritized.

[rowillia]

I'd also love to get #3666 in as well, it's bitten us as we've picked up types in some of our codebases.

[JukkaL]

I'd like to see #3669 fixed (if the fix is simple enough) before release. I'll probably have a look at it on Monday unless somebody can come up with a PR before that.

[JukkaL]

I'll check #3666 on Monday at the latest. I haven't had a chance to have a careful look yet but it looks simple enough.

[JukkaL]

#3665 probably won't make it to this release :-(

[JukkaL]

0.520 is now out: http://mypy-lang.blogspot.co.uk/2017/07/mypy-0520-released.html

Thanks to everybody who contributed to this release! Feature freeze has been lifted.

We are thinking about doing a 0.521 bug fix release later this week.