4 ms·

If I remember correctly, Typescript felt the same way for quite a long time

• nurettin 3y ago
  It did, especially in the late 2013 and early 2014s. But then the type repositories quickly caught up. Python package authors usually shy away from such endeavours, especially those who use kwargs in order to configure large classes. pygann comes to mind.
  • maleldil 3y ago
    Python has also seen a sizable movement towards using types as part of the design, such as Typer, FastAPI and Pydantic. Existing mainstream libraries are also slowly adopting types, such as pandas and numpy (including `numpy.typing`). For the latter cases, it's not easy because typed APIs require different principles than dynamic/duck-typed ones. Still, I think it's safe to say that the community is trending towards more typing over time, especially greenfield projects. Personally, all my new projects are 100% typed, with type-safe wrappers around untyped libraries. For what it's worth, since Python 3.12 (or with typing_extensions for earlier versions), it's also possible to use Unpack and TypedDict to type kwargs.
  • nerdponx 3y ago
    What is pygann? It's not on PyPI.
    • nurettin 3y ago
      it was pygad
  • int_19h 3y ago
    Python was always much more dynamically typed than JS, and it also became the prevailing approach in the ecosystem.