What to use for finding as many syntax errors as possible.

[Antoon Pardon]

Op 10/10/2022 om 00:45 schreef Cameron Simpson:
> On 09Oct2022 21:46, Antoon Pardon <antoon.pardon at vub.be> wrote:
>>> Is it that onerous to fix one thing and run it again? It was once 
>>> when you
>>> handed in punch cards and waited a day or on very busy machines.
>>
>> Yes I find it onerous, especially since I have a pipeline with unit 
>> tests
>> and other tools that all have to redo their work each time a bug is 
>> corrected.
>
> It is easy to get the syntax right before submitting to such a 
> pipeline.  I usually run a linter on my code for serious commits, and 
> I've got a `lint1` alias which basicly runs the short fast flavour of 
> that which does a syntax check and the very fast less thorough lint phase.

If you have a linter that doesn't quit after the first syntax error, 
please provide a link. I already tried pylint and it also quits after 
the first syntax error.

-- 
Antoon Pardon