In 2019, a total of 9,218,822 packages were downloaded, taking the total to 14,745,528. This saved 128 years 5 months during 2019, taking us to over 172 years saved overall. 37TB of files were downloaded, taking the total to 51TB.
Each month had over 500,000 downloads, reaching over 1 million in November and December:
Each month saved over 7 years, topping out at 17 years:
At the start of the year, most downloads were for Python 3.5 which is in Raspbian Stretch, but as soon as Buster was released, Python 3.7 began to take over:
There’s a steady trickle of Python 2.7 downloads, but note that this does not fairly represent usage as we do not provide wheels for Python 2, so any downloads are for pure Python packages. There’s also a small number of people using out-of-distribution Python versions 3.6 and 3.8 (the red section). We are barely seeing any Python 3.4 downloads, perhaps due to the fact Raspbian Jessie was never configured to use piwheels, and the pip in Jessie needs upgrading to be able to use it.
The Pi 2, 3 and 4 all identify as armv7l, whereas Pi 1 and Zero are armv6l. armv7l usage has always accounted a huge majority of downloads (88% in 2018), and it’s pretty much stayed around that mark through 2019:
The vast majority of downloads are from Raspbian (over 90%). As observed with Python versions, much of the usage switched from Stretch to Buster after its release in July:
There was a noticeable bump of users reporting Raspbian (testing) before Buster was officially launched.
Our busiest hour is between 7pm-8pm. All afternoon/evening UTC we are at our busiest:
There’s no Raspbian release scheduled this year, so we won’t be introducing any new Python versions until Raspbian Bullseye arrives mid-2021.
We have been working on a few new features, including a JSON API which dynamically populates our project pages, and which you’ll be able to use to programmatically find out info about what packages we provide. We have also made it possible to calculate apt dependencies for a wheel based on packages providing required shared object files, as described in a previous post, although it’s not yet been calculated for older projects. Hopefully we’ll get this sorted, and it being included in the project pages JSON API will make it even easier. We’re working on deploying these changes very shortly!
The piwheels project wouldn’t be possible without considerable support from Mythic Beasts, who provide storage and cloud Pis. The Pi platform is so straightforward, it’s been a pleasure to use, allowing us to scale up builder Pis with ease. We highly recommend using this (very affordable) service for real Pi testing for your projects.