Output errors in machine-friendly format?

[alok]

Elm has the option to output errors as JSON (via a flag), and something like that is handy for writing tooling around it. I'm trying to integrate pytype into ALE and this would make it a lot easier.

[rchen152]

Would CSV format work? pytype-single has an --output-errors-csv flag (https://github.com/google/pytype/blob/master/pytype/config.py#L183) that we could expose in pytype.

[alok]

Probably will be fine.

[martindemello]

closing this, reopen if csv is insufficient for some use case.

[kovasap]

@alok did you ever complete this integration?

[rchen152]

Responding to #634 made me realize that we closed this issue without ever actually exposing --output-errors-csv to analyze_project, and there's clearly still an appetite for this feature, so reopening this issue.

[martindemello]

tagging this "good first issue"; plumbing the csv output from pytype-single through the stack would not require much deep knowledge of pytype

[djh82]

A supported, standard format would be nicer? Many CI systems can already process formats like PEP8, do we really want another one?

[jollypolly123]

Would fixing this just involve adding it as an arg to analyze_project/parse_args.py and getting the errors.csv like single_test.py?

[martindemello]

@jollypolly123 that would be the first step, but we would also need to collect the errors.csv from multiple runs of pytype-single and combine them into a single csv file.