Python 2 feature freeze (and removal of support)

[JukkaL]

Since Python 2 reached its EOL Jan 1 2020 (over two years ago), I think that it's time to not actively improve Python 2 support any more.

Details:

1. We won't accept new PRs that improve Python 2 support, unless they fix a significant regression.
2. We won't drop or degrade existing support for Python 2, for now. Python 2 will become unsupported at some point, but at least not until the second half of 2022 (details TBD).
3. Existing open Python 2 PRs can still be merged if they seem useful and low risk.
4. We can remove some Python 2 specific test cases if they are hard to maintain (e.g. require runtime access to Python 2).

cc @sobolevn who has done some recent work on Python 2 features.

[hauntsaninja]

#12202 was a pretty significant Python 2 regression and we've only gotten the one report from it :-)

[JelleZijlstra]

Worth noting that mypy appears to be the last type checker to still support Python 2. Pyre and pyright never supported it; pytype and pyanalyze dropped support last year. We also stopped updating the typing backport for Python 2. Once mypy drops Python 2 support, we should also remove the Python 2 stubs from typeshed.

[hauntsaninja]

Is Python 2 support still important for Dropbox?

[JukkaL]

Is Python 2 support still important for Dropbox?

No.

[JukkaL]

Worth noting that mypy appears to be the last type checker to still support Python 2.

I think that PyCharm still supports Python 2.

There are also quite a few downloads of the typing backport for Python 2 (on the order of 150k-200k downloads per day): https://pypistats.org/packages/typing

[JukkaL]

I closed existing Python 2 specific issues (thanks @AlexWaygood for tagging them!). We don't need to keep open any new issues that only affect Python 2, unless it is a regression in a recent mypy release.

[emmatyping]

I found out that there is a regression in typeshed that makes type checking Python 2 code impossible in 0.950 python/typeshed#7367 (comment)

It seems that no one else has Python 2 installed, so all the relevant tests were getting skipped, including in CI.

Since we effectively haven't been testing Python 2 support, I think we should just drop support in the next release. I don't think there is much to be gained from fixing this issue, and I don't really want to ask anyone who maintains typeshed to fix it :)

Perhaps we can post on the blog that we are considering dropping support for Python 2 in 0.960 in a blog post prior to the release so that if anyone has a problem with it they can open an issue (or better yet comment on this one).

Also to clarify: I am not worried about this specific issue, more that we aren't really checking Python 2 in CI anymore, so I think we shouldn't claim to support it.

[JukkaL]

Does the Python 2 issue cause serious problems outside tests? I was able to type check simple Python 2 code examples without problems, at least.

[emmatyping]

I think anything using set, mutable set or anything that inherits from AbstractSet will probably be broken.

[JukkaL]

The Python 3 stubs apparently generate similar errors, but they are ignored. Example:

class set(MutableSet[_T], Generic[_T]):
    ...
    def __ior__(self: Self, __s: AbstractSet[_T]) -> Self: ...  # type: ignore[override,misc]

Since we don't normally report errors from typeshed stubs, the issue seems benign. I'll prepare a typeshed PR that ignores the errors in the Python 2 stubs as well.

[JukkaL]

Suggested fix to the Python 2 issues: python/typeshed#7894

[hauntsaninja]

It is now second half of 2022 — can we drop support? I'm sure people who are happy with Python 2 will also be happy pinning to an older version of mypy; we can even have --python2 automatically suggest that.

[JukkaL]

The second half of 2022 starts on July 1st, so we are almost -- but not quite -- there.

[JukkaL]

It's now the second half of 2022, so we can finally drop Python 2 support.

List of steps (this is probably incomplete):

• Wait until typeshed removes Python 2 stubs.
• Remove test cases specific to Python 2.
• Make the -2, --py2 and --python version 2.7 options print an error and suggest using an older version of mypy.
• Sync typeshed (removes Python 2 stubs).
• Remove Python 2 specific things in the documentation.
• Remove Python 2 parser (mypy/fastparse2.py).
• Remove support for pip install mypy[python2] and the optional typed-ast dependency on recent Python versions.
• Remove Python 2 specific type checker logic.

[sobolevn]

I also propose to drop six / similar libraries support, since python2 is no longer supported.

#13567

[emmatyping]

Won't some Python 3 code that was ported from Python 2 still have six usage in it?

[ilevkivskyi]

Yeah, I can add +1 to @ethanhs comment. There is some code that runs on Python 3, but is still being cleaned up from all the six things.

[SamB]

I think you need to add a new version to the readthedocs config now that is also pinned to an older version so that people can still easily get the needed docs when they're dealing with legacy Python 2 stuff?

[SamB]

(It might also be worth adding something somewhere to the documentation about the removed support?)

[hauntsaninja]

Closing, since this is done.

Use of the Python 2 options with new mypy has a nice error message which should be enough documentation.

Not planning on more readthedocs config for this. Python 2 is dead. I assume if people still have Python 2 codebases they have bigger problems than tweaking their mypy config. And git is always forever. If you feel strongly, open another issue and see if it gets upvotes.

[schlamar]

@hauntsaninja It would be really great if you could re upload the last documentation with Python 2 support on readthedocs as an additional version. Right now, it has become nearly impossible to find online useful information regarding type hints for Python 2.