You just have to do it manually in Python or rely on systems like mypy to get 'static' checking.
It can be useful to rely on duck typing though if you don't want to have to re-implement or inherit from an existing base class to use a higer order function.
If the function is written in a way where all it needs is specific methods or parameters from its input objects, you can really save on interface bloat.
But if someone is used to writing statically typed code and has to deal with that it can create a lot of confusion and I always end up writing a ton of override signatures either in my code or in a .pyi sidecar so whoever is using it can still get some form of feedback that what they're doing is okay. Or at the very least putting that information in the docstring so people can read the docs as they're using the function.
Those are in no way incompatible.
Of course not, the syntax is making the type system obvious tho
You just have to do it manually in Python or rely on systems like mypy to get 'static' checking.
It can be useful to rely on duck typing though if you don't want to have to re-implement or inherit from an existing base class to use a higer order function.
If the function is written in a way where all it needs is specific methods or parameters from its input objects, you can really save on interface bloat.
But if someone is used to writing statically typed code and has to deal with that it can create a lot of confusion and I always end up writing a ton of override signatures either in my code or in a .pyi sidecar so whoever is using it can still get some form of feedback that what they're doing is okay. Or at the very least putting that information in the docstring so people can read the docs as they're using the function.