[Python-ideas] Wheels For ...

Steve Dower steve.dower at python.org
Sun Sep 6 21:22:19 CEST 2015

On 06Sep2015 1033, Sven R. Kunze wrote:
> The logical conclusion
> would be that PyPI should build wheels for the developers for every
> python/platform combination necessary.

This would be a wonderful situation to end up in, but the problem is 
that many wheels have difficult source dependencies to configure. It is 
much easier for the developers who should already have working systems 
to build the wheel themselves then it would be either for them to 
provide/configure a remote system to do it, or for the end-user to 
configure their own system. (And if it can't be tested on a particular 
system, then the developer probably shouldn't release wheels for that 
system anyway.)

What I would rather see is a way to delegate building to other people by 
explicitly allowing someone to add wheels to PyPI for existing releases 
without necessarily being able to make a new release or delete old ones. 
There is some trust involved, but it could also enable more ad-hoc 
systems of building wheels through Travis/Jenkins/VSO/etc. automation 
without needing to reveal login information through your repo (i.e. you 
give the "Jenkins-wheel" user permission to publish wheels for your 

Not sure how feasible this is, but I'd guess it's easier than trying to 
run our own build servers.


More information about the Python-ideas mailing list