Open paternal opened 5 years ago
@paternal thanks for addressing the idea. This was something I had originally planned on but cut from the initial implementation of the site.
I definitely would like to have something like this eventually, and I think it might be feasible within the context of a relatively short fixed time window. I'll do some digging into the data and see what I can come up with as a potential solution.
I am also interested in this, in order to make data-driven decisions about how long to support a major version of a given package I maintain.
It would also be great to be able to see facet the version data by python version as well. That way, we wouldn't have to manually run queries like the ones in https://github.com/marshmallow-code/marshmallow/issues/1274#issue-462767119 (query: https://bigquery.cloud.google.com/results/spring-house-88715:US.bquijob_b5a519f_16bc3aca696).
Thanks for this project!
Thanks for the project, it's great!
This would be extremely useful. Both out of curiosity and to make better decisions about supporting old versions etc.
Is there anything we can do to encourage pypistats.org to add this?
FYI https://pepy.tech/project/pytest has per-version download stats, though not any of the other breakdowns from pypistats.
FYI https://pepy.tech/project/pytest has per-version download stats, though not any of the other breakdowns from pypistats.
What I'd like to know is : version 1.0.0 of my package
foobar
was downloaded X times, while version 1.1.0 was downloaded Y times.This would give an idea of my package popularity over time, without requiring to record download count of every single day since the beginning of time (which is done with the overall endpoint of the API, only for a recent history).
(I just discovered this repo. For a long time, I did want to get pypi download counts without having to manipulate Big Query myself; http://pypistats.org solved this. Thanks!)
-- Louis