My use case may actually be very common: I develop an open source project on github that uses travis-ci. This means rebuilding the testing environment with each build, or else doing hacky things. Any open source python project that depends on lxml could/should be doing something similar. By uploading a wheel you might save 2-10 minutes from each build, of which we certainly have dozens per day, so the overall savings for just typing "python setup.py bdist_wheel upload" could be huge.
Continuing to use a source distribution is *not* an option. The question is simply whether we can stick with the standard pypi or have to roll something ourselves that will, unfortunately, not benefit the rest of the community.
My use case may actually be very common: I develop an open source project on github that uses travis-ci. This means rebuilding the testing environment with each build, or else doing hacky things. Any open source python project that depends on lxml could/should be doing something similar. By uploading a wheel you might save 2-10 minutes from each build, of which we certainly have dozens per day, so the overall savings for just typing "python setup.py bdist_wheel upload" could be huge.
Continuing to use a source distribution is *not* an option. The question is simply whether we can stick with the standard pypi or have to roll something ourselves that will, unfortunately, not benefit the rest of the community.