On 4/12/21 7:43 PM, Hugh Fisher wrote:
Having a type checker run before the Python interpreter in our
current day continuous build/integration environment adds a
second step
This is very similar to statically typed languages. They also have two
steps:
* There is the first step that checks the types but does not run the
program. In C/C++, this is the compiler, in Python it is "mypy".
* There is the second step that runs the program but does not check
the types. In C/C++, this is running the executable, in Python it is
"python".
In Python, we can skip the first step, and perhaps that is the source of
your concern. I doubt anyone that has adopted type hinting in Python
will forget to run mypy, especially in a CI environment like you consider.
--Ned.
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/python-dev@python.org/message/STHJTBL6RL2JNKS47IST3K6EFN2WIMSV/
Code of Conduct: http://python.org/psf/codeofconduct/
