Skip to content

Completion statistics #4179

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

Closed
srittau opened this issue Jun 4, 2020 · 3 comments
Closed

Completion statistics #4179

srittau opened this issue Jun 4, 2020 · 3 comments

Comments

@srittau
Copy link
Collaborator

srittau commented Jun 4, 2020

I am just throwing this out here as an idea: It would be useful to generate per-file statistics about their completion. I.e. the number of annotated arguments, fields, and return values vs. the unannotated number. This would obviously not count Any annotations as unused, although Any annotations could possibly be counted separately as well. This could also mark files that have an incomplete comment.

@srittau
Copy link
Collaborator Author

srittau commented Jun 4, 2020

This could be a GitHub action that runs once per day on master and generates a GitHub pages webpage. Maybe it could also store historical data somewhere.

@hauntsaninja
Copy link
Collaborator

I believe we can use mypy to at least report missing annotations by running with --disallow-untyped-defs --warn-incomplete-stub (python/mypy#8917 (comment)).
We can also run stubtest without --ignore-missing-stub to track things that are missing entirely from the stubs (although this can't work reliably for missing fields).

@AlexWaygood
Copy link
Member

AlexWaygood commented Jan 8, 2023

This information is now collected, and auto-updated twice every day, at https://alexwaygood.github.io/typeshed-stats/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants