-
Notifications
You must be signed in to change notification settings - Fork 22
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
support of json format #62
Comments
JSON shouldn't be too much work, so probably yes. YAML is a bit of a mess and would require some external library like PyYAML, so it would be interesting to know what's the actual benefit over JSON. Concerning the actual structure: Are there any existing tools or applications you would like to use the output with? If yes, it might be sensible to support an existing format (similar to |
There was a adhoc requirement to count the source code lines of multiple repositories. Json format is more easy to parse than summary type output by automation. that's the only intent to have Json format support. |
Removed YAML from subject as there does not seem to be a compelling reason to support it. |
#62 Added JSON as additional output --format.
Just merged this into the master branch. Should make it to PyPI sometime next week. You can already read the documentation at https://pygount.readthedocs.io/en/latest/json.html. |
…was a copy and paste of "files per second".
#62 Fixed computation of runtime statistic "lines per second".
Pygount 1.3.0 with JSON support is now available from PyPI. |
Can we have json and yaml output format support.
The text was updated successfully, but these errors were encountered: