20
votes

Since static typing is available in Python 3.6, is it possible to force static typing for a python project or set of python files?

2
Static typing is not available in python yet. Type hints or type annotations are for static analyzers like mypy which is not the same as static typing. - phd
@Drako The TypeError is from normal Python operation. i.e., if you removed the hints, it would still raise an error. ('this is ' + <int> raises it). def f(s: str) -> str: return 0 and then calling f(0) does not raise a TypeError for me (Python 3.6.1) - Artyer
@Drako: there is no type-checking at runtime as per PEP484: python.org/dev/peps/pep-0484 - Ando Jurai

2 Answers

14
votes

You can use annotations in Python3, which might help you get some benefits of static typing.

However if static typing were to be completely enforced in Python, then it won't be Python anymore. It's a duck-typed dynamic language, and would loose all dynamism as a result. If you really intend to use a statically-typed language, you are better off not using Python.

12
votes

I think you cannot force static typing but you can use a checker as mypy.

According to line 2 of The Zen of Python by Tim Peters, you have "Explicit is better than implicit." Static typing is a good thing, but "Simple is better than complex." ...

$ python3.6
>>> import this
The Zen of Python, by Tim Peters

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!