- The data update begins at 01:00:00 UTC and should take less than 10 minutes. + The data update begins at 01:00:00 UTC and should take about 10 minutes.
The cumulative download counts consider only the download records which are not from a known set of PyPI mirror
applications, namely bandersnatch, z3c.pypimirror, Artifactory, and
- devpi. In other words, the cumulative download counts take the sum of the downloads from the Without_Mirrors
- dataset from the chart.
+ devpi. In other words, the cumulative download counts take the sum of the downloads from the
+ Without_Mirrors dataset from the chart.
- The With_Mirrors and Without_Mirrors are not mutually exclusive sets of download counts like the - other segmentations provided. In fact, the Without_Mirrors downloads are a subset of the downloads in - With_Mirrors. + The With_Mirrors and Without_Mirrors downloads are not mutually exclusive sets of download counts + like the other segmentations provided. In fact, the Without_Mirrors downloads are a subset of the + downloads in With_Mirrors.
- Some entities will create a mirror, or clone, of the PyPI repository using a tool like bandersnatch
- for the sake of security or availability. This means that their mirror repository regularly syncs with PyPI by
- downloading all of the Python packages available. Those downloads are recorded by PyPI with bandersnatch
- as the user-agent. pypistats.org filters downloads from known mirrors from the version and system segmentations on
- the website. You will see also that on days in which you release a new version of your package there will be many
- more downloads from mirrors, as active mirrors will sync with PyPI by downloading those new releases.
+ Some entities will create a mirror, or clone, of the PyPI repository using a tool like bandersnatch
+ for the sake of security or availability. This means that their mirror repository regularly syncs with PyPI by
+ downloading all of the Python packages available (and versions thereof) that it does not already have. Those
+ downloads are recorded by PyPI with bandersnatch as the user-agent. You will see also that on days
+ in which you release a new version of your package there will be many more downloads from mirrors, as active
+ mirrors will sync with PyPI by downloading those new releases.
- The existence of mirrors means that the downloads provided by PyPI and BigQuery add uncertainty to the actual - usage of Python packages. One might expect that mirrors will mask end-user downloads for more commonly used - packages while simultaneously inflating the download counts of less common ones. We can't really be sure because - the mirrors don't report subsequent downloads back to PyPI. + pypistats.org filters downloads from known mirrors from the version and system segmentations on the website. + Downloads by mirrors are intentionally excluded from download breakdowns because they do not + represent end-users of the software. Instead, they serve as an alternative provider to other end-users on + a separate (sometimes private) network.
- Downloads by mirrors are intentionally excluded from download breakdowns on pypistats.org because they do not - represent end-users of the software. Instead, they serve as an alternative provider to other end-users on a - separate (sometimes private) network. + The existence of mirrors means that the downloads provided by PyPI and BigQuery come with some uncertainty with + respect to the actual aggregate usage of Python packages. One might expect that mirrors will mask end-user + downloads for more commonly used packages while simultaneously inflating the download counts of less common + ones. This uncertainty is difficult to quantify because the mirrors don't report subsequent downloads back to + PyPI.
- We can, however, assume that PyPI serves a significant proportion of the Python community's packaging downloads. - Hopefully significant enough that the quantities provided here are relevant to package maintainers and - representative of their users. There are other distributors like Conda which also serve python packages, but - their download data is not available like PyPI's as far as I'm aware, and thus are not incorporated in this website. + One can, however, assume that PyPI serves a significant proportion of the Python community's packaging + downloads. Hopefully significant enough that the quantities provided here are representative of their users and + relevant to package maintainers. There are other distributors, like Conda, which also serve python packages, + but their download data is currently not publicly available at the event level like PyPI's, and thus are not + incorporated into the metrics on this website.
The intent of disregarding mirrors is to provide metrics that reflect end-user download aggregation. @@ -79,7 +83,7 @@
Downloads from CI/CD tools are included in all metrics. There is currently no easy way to attribute downloads to - deployment tools. + build/deployment tools.
{% endblock %}