-
Notifications
You must be signed in to change notification settings - Fork 33
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
feature request - trend support #47
Comments
I'm not sure if it belongs as part of pypinfo, and it'll burn through a lot of quota, but I've made a wrapper around pypinfo to do something like this. (I'd be happy to contribute it or parts of it here, if that makes sense.) See:
Examples of further processing of downloaded data: |
suv27
pushed a commit
to suv27/pypinfo
that referenced
this issue
Oct 5, 2019
suv27
pushed a commit
to suv27/pypinfo
that referenced
this issue
Oct 5, 2019
suv27
pushed a commit
to suv27/pypinfo
that referenced
this issue
Oct 5, 2019
suv27
pushed a commit
to suv27/pypinfo
that referenced
this issue
Oct 5, 2019
suv27
pushed a commit
to suv27/pypinfo
that referenced
this issue
Oct 5, 2019
Adiciona método de not_found e not_relation ofek#47
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
It would be great to be able to tell project tendencies. E.g are my monthly usage going up or down? This is already possible with playing around the start and end date, but what about providing a builtin way of this, that does not require shell scripting it?
The text was updated successfully, but these errors were encountered: