provide bdist_eggs of every release on every platform

[Zooko Wilcox-O'Hearn]

The Tahoe-LAFS project has a ticket to build and host bdist_eggs of pyOpenSSL on all of our supported platforms:

http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1014#comment:4

Maybe we could cooperate on this. We could build some bdist_eggs or ask volunteers on our mailing list to do so. Or we could set up automation. We currently use buildbot to automatically build and upload bdist_eggs of pycryptopp (http://tahoe-lafs.org/buildbot-pycryptopp/waterfall ) and zfec (http://tahoe-lafs.org/buildbot-zfec/waterfall ). The same thing should in principle work for pyOpenSSL.

[Zooko Wilcox-O'Hearn (zooko)]

Let me know if you're working on this ticket and want help.

[Zooko Wilcox-O'Hearn (zooko)]

Some people are contributing eggs of pyOpenSSL, among other libraries, to Tahoe-LAFS:

https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2000

[Alex Gaynor (alex-gaynor)]

At this point a desire for eggs should probably be superceded by having wheels, which are the new standard for binary distribution of Python projects.

[Zooko Wilcox-O'Hearn (zooko)]

One doesn't preclude the other.

For what it is worth, there seem to be limitations with the wheel design that might cause a problem for my uses. One is that wheel doesn't attempt to make binaries for linux. Of course, there's a good reason for that, which is that it is impossible to make one that is actually reliable portable to multiple linuxes. But, distutils/setuptools/distribute/new-setuptools/eggs make a half-assed attempt at it, and that might be better for some uses than wheel's principled refusal to try at all.

[Jean-Paul Calderone (exarkun)]

I've been making some progress on <https://bugs.launchpad.net/pyopenssl/+bug/1152689>. Once this is resolved, I don't think binary packages of pyOpenSSL will be required anymore. Instead, binary packages of cryptography will be necessary to provide the desired user experience.