On Fri, Nov 26, 2021 at 12:02 PM Rob Cliffe via Python-ideas <[email protected]> wrote: > On 26/11/2021 00:12, Steven D'Aprano wrote: > > Personally, I think that this is the right design. People can pick and > > choose which, if any, linter they use, and how strict they want it to > > be. But I can also understand that some people might want the > > interpreter to also have a built-in linter to flag mistakes. > > > > > +1. This just feels like it has "this is a job for linters" written all > over it. YMMV.
Agreed. Though there are a small number of cases where the language itself offers helpful warnings: >>> x = 1 >>> x is 2 <stdin>:1: SyntaxWarning: "is" with a literal. Did you mean "=="? False but these are reserved for situations that are very definitely, but more subtly, wrong (since this code will often appear to work just fine due to small-int caching). Chrisa _______________________________________________ Python-ideas mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/ANOHILN7XAFUEVWBVD3SUSP33FENYXFD/ Code of Conduct: http://python.org/psf/codeofconduct/
