Make support for type comments optional

PEP 484 (and therefore the current typing spec) implies that type checkers must support the old "type comment" syntax. However, this syntax is unnecessary since Python 3.6 and PEP 526, so there is little reason for new type checkers to support it.

I think we should no longer make support for type comments mandatory. We can keep describing the intended semantics of type comments, but say that type checkers are free to drop support for them. Code that is intended to work across type checkers (e.g., library stubs) should not use them.

PEP 484 (and therefore this spec) imply that type checkers must support the old "type comment" syntax. However, this syntax is unnecessary since Python 3.6 and PEP 526, so there is little reason for new type checkers to support it.

I think we should no longer make support for type comments mandatory. We can keep describing the intended semantics of type comments, but say that type checkers are free to drop support for them. Code that is intended to work across type checkers (e.g., library stubs) should not use them.

(Note that this does not include # type: ignore comments. Those are still useful and should continue to work.)

This isn't urgent so I'll likely not pursue this very soon, but I'm filing this issue to keep track of the idea. I previously filed JelleZijlstra/typing-spec#1, where one person spoke up because they still like type comments, but I'm planning to archive that repo.

Lies die Behandlung von Typkommentaren in der Typing-Spezifikation zusammen mit PEP 484 und PEP 526 und prüfe anschließend die frühere Diskussion JelleZijlstra/typing-spec#1. Die Aufgabe ist erledigt, wenn die Spezifikation Typprüfern erlaubt, die gewöhnliche Unterstützung für Typkommentare wegzulassen, während die Anforderung für # type: ignore-Kommentare beibehalten und die Kompatibilitätshinweise erklärt werden.