Don't worry about me. I mean all projects that do not have people and resources for this stuff. People just want to write Python and be done with it.
Without type hints they wrote Python and if they run it and tests pass then it works. Now they write Python code that can be wrong but they don't find out unless they also run an extra tool.
The fact that it requires CI now is a good illustration of the problem;)
I don't understand who the "just want to write Python and be done with it" demographic is. If you're a developer, it makes sense to do things well, if you aren't and you're writing small one-off scripts, you can do fine without type hints.
Anyone who can write and run a test can also call "mypy ." on their project.
So when you see type declarations in Python, you cannot trust them the way you can trust them in Rust or TypeScript. Outright wrong types that make zero sense cause no errors, no test failures, etc. Type validation is reduced to the level of linter, and no one really cares about the linter the same way as they care about working code.
This gets people new to static typing into bad habits and loses the main benefit of type system.
Don't worry about me. I mean all projects that do not have people and resources for this stuff. People just want to write Python and be done with it.
Without type hints they wrote Python and if they run it and tests pass then it works. Now they write Python code that can be wrong but they don't find out unless they also run an extra tool.
The fact that it requires CI now is a good illustration of the problem;)