A more useful and less divisive future for typing?

[hauntsaninja (Shantanu Jain)]

@pf_moore

I think I agree with this, but for me the “fence” is very much a social one, rather than a technical one. We need to make not having type annotations socially acceptable again, …

@smontanaro

Maybe, like JavaScript, someone will eventually feel obligated to write a book entitled Python: The Good Parts. If so, I hope they leave out static type annotations.

I’m not the right person to be delivering the message, but I believe in informed decisions, so I went ahead an opened a PR with a proposed anti-pitch. Add an anti-pitch for typing by hauntsaninja · Pull Request #1477 · python/typing · GitHub. I’m hopeful we can all band together and make Skip’s dream of writing the book “Python Type Checking: The Bad Parts” come true

@mikeshardmind

this is only pointing out how the current status quo leaves more to type checkers in a way that decreases the usefulness of typing from a perspective of those wanting type safety from it.

We’re a little bit off topic from Mike’s initial post (which is a contrary viewpoint to most of the folks in this thread), but I did make sure to make mention of this in the anti-pitch.

Finally, it also seems like a (surprising to me) amount of complaints here are about VSCode behaviour (jump to definition, docstring hover, etc). Has someone tried surfacing this to the VSCode team?