"Transitioning" an incredibly stupid goal, which unfortunately is becoming trendy among engineers who have nothing better to do. Typed Python is not better or

"Transitioning" an incredibly stupid goal, which unfortunately is becoming trendy among engineers who have nothing better to do. Typed Python is not better or worse than untyped Python, it has different tradeoffs. If you're setting a goal to "transition" your application, it means you don't understand what those tradeoffs are. You have a non-nuanced thinking is "types equals good" or "new equals good". > then add more complex types or even construct types for your application In other words, your intention is to add complexity to your application, while preserving it's functionality. Neither engineering nor business as a whole is going to benefit from additional complexity. The "edge case" where complexity can be beneficial is where the ratio of library maintainers to library users differs by orders of magnitude. E.g. if you have a library with 5 maintainers and 1,000,000 users, then types can be a net positive.