On Thu, Dec 10, 2020 at 09:18:32PM -0000, redrad...@gmail.com wrote: > I do not want to make type-checker a part of CPython, I just what > options that will allow to run python with first some type-checker ...
Okay. So we have a standard interpreter option to run a type-checker. Then tomorrow someone says that we need a standard interpreter option to run black, or another code reformatting tool. Then the day after, someone else says Python needs a standard option to run a linter like Jedi or PyFlakes over the code. Then the day after, someone else wants an option to run a test framework before running your code. Run the tests, and if they pass, run the code. And the next day after that, another person insists that there should be a standard interpreter option to run a code-coverage utility. And the following day, someone insists that Python needs an option to run a fuzz-tester. And then someone demands a standard option to run code refactoring tools. And somebody wants a special option to run a utility to vacuum their database before running their code. And then... Where does it end? Does the Python interpreter need to have a thousand special options to check for the existence of a thousand different tools and run them? You are probably thinking, "But this is silly! None of those things are so important that Python needs to support them with a standard runtime option. Just write a script!" And I totally agree. The only difference is you think that we need to make a special exception for type-checking. Why should the interpreter make *type checking* a special option and not all of the others? -- Steve _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/W5HCZGI7SH5ABWSSVHPRO3P3E5CAWLEK/ Code of Conduct: http://python.org/psf/codeofconduct/
