Skip to content

/ pytype

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Output errors in machine-friendly format? #92

Open
alok opened this issue Jun 28, 2018 · 7 comments
Open

Output errors in machine-friendly format? #92

alok opened this issue Jun 28, 2018 · 7 comments
Labels
enhancement good first issue

Comments

@alok
Copy link

@alok alok commented Jun 28, 2018

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
Copy link
Contributor

@rchen152 rchen152 commented Jun 29, 2018

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
Copy link
Author

@alok alok commented Jun 29, 2018 •
edited

Probably will be fine.
@martindemello
Copy link
Contributor

@martindemello martindemello commented Jul 20, 2018

closing this, reopen if csv is insufficient for some use case.
@UfoRobot UfoRobot mentioned this issue Jul 22, 2019
Open
@kovasap
Copy link

@kovasap kovasap commented Aug 5, 2019

@alok did you ever complete this integration?
@rchen152 rchen152 mentioned this issue Jul 30, 2020
Closed
@rchen152
Copy link
Contributor

@rchen152 rchen152 commented Jul 30, 2020

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.
@rchen152 rchen152 reopened this Jul 30, 2020
@martindemello
Copy link
Contributor

@martindemello martindemello commented Jul 30, 2020

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

@davidhart82 davidhart82 commented Oct 2, 2020

A supported, standard format would be nicer? Many CI systems can already process formats like PEP8, do we really want another one?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement good first issue
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants
@martindemello @davidhart82 @rchen152 @alok @kovasap
You can’t perform that action at this time.