add python typing tools

Author: copdips

docs/posts/2025/2025-02-01-python-type-hints.md

@@ -3,21 +3,28 @@ authors:
 - copdips
 categories:
 - python
+- linter
 comments: true
 date:
   created: 2025-02-01
+  updated: 2025-06-28
 ---
 
 # Python Type Hints
 
+Python is a dynamic language, which means you don't need to declare the type of a variable. But in reality, once you go for some complexity previously (even for small project nowadays), you need to declare the type of a variable.
+One of biggest focus of recent Python releases is to improve the type hints. My first memory of typing hint is back to Guido when I heard about he started developing the MyPy module for Dropbox, who needed to migrated code base from Python 2 to Python 3. (Most of this team moved to Microsoft now.)
+Typing hint becomes more important when we start building applications (even scripts) with IDE, or using AI tools, typing hint help the IDE and AI to understand much better the code base, so provide better code completion, code analysis, etc.
+We can see the same thing in TypeScript vs traditional JavaScript.
+
+<!-- more -->
+
 ## typing module vs collections module
 
 Since Python 3.9, most of types in `typing` module is [deprecated](https://docs.python.org/3/library/typing.html#deprecated-aliases), and `collections` module is recommended.
 
 Some types like: `typing.Any`, `typing.Generic`, `typing.TypeVar`, etc. are still not deprecated.
 
-<!-- more -->
-
 ### Aliases to Built-in Types
 
 | Deprecated Alias   | Replacement |
@@ -117,4 +124,37 @@ Some types like: `typing.Any`, `typing.Generic`, `typing.TypeVar`, etc. are stil
 
 !!! note "(Python 3.9+) Both `typing.Sequence` and `typing.Collection` are [deprecated aliases](#typing-module-vs-collections-module)."
 
-## To be continued
+## Typing tools
+
+### MyPy
+
+Ref. MyPy in [this post](../2021/2021-01-04-python-lint-and-format.md#mypy).
+
+### Pyright && Pylance
+
+Ref. Pyright in [this post](../2021/2021-01-04-python-lint-and-format.md#pyright).
+
+[Pylance](https://github.com/microsoft/pylance-release#readme) is the Microsoft backed Pyright extension for VSCode.
+
+### RightTyper
+
+During an internal tech demo at my working, I heard about [RightTyper](https://github.com/RightTyper/RightTyper), a Python tool that generates type annotations for function arguments and return values.
+It’s important to note that RightTyper doesn’t statically parse your Python files to add types; instead, it needs to run your code to detect types on the fly. So, one of the best ways to use RightTyper is with python `-m pytest`, assuming you have good test coverage.
+
+### ty
+
+[ty](https://github.com/astral-sh/ty) represents the next generation of Python type checking tools. Developed by the team behind the popular [ruff](https://docs.astral.sh/ruff/) linter, ty is implemented in Rust for exceptional performance.
+It functions both as a type checker and language server, offering seamless integration through its dedicated [VSCode extension ty-vscode](https://github.com/astral-sh/ty-vscode).
+
+While Ruff excels at various aspects of Python linting, type checking remains outside its scope.
+ty aims to fill this gap, though it's currently in preview and still evolving toward production readiness.
+The combination of Ruff and ty promises to provide a comprehensive Python code quality toolkit.
+
+### pyrefly
+
+[pyrefly](https://pyrefly.org/) emerges as another promising entrant in the Python type checking landscape.
+Developed by Meta and also written in Rust, pyrefly offers both type checking capabilities and language server functionality.
+While still in preview, it demonstrates the growing trend of high-performance Python tooling implemented in Rust.
+
+The tool integrates smoothly with modern development environments through its [VSCode extension refly-vscode](https://marketplace.visualstudio.com/items?itemName=meta.pyrefly), making it accessible to a wide range of developers.
+Its backing by Meta suggests potential for robust development and long-term support.