[tahoe-dev] [tahoe-lafs] #1065: provide binary eggs of PyCrypto for our supported platforms

tahoe-lafs trac at tahoe-lafs.org
Sun Oct 31 06:08:52 UTC 2010

#1065: provide binary eggs of PyCrypto for our supported platforms
     Reporter:  zooko      |       Owner:  somebody                                
         Type:  defect     |      Status:  new                                     
     Priority:  major      |   Milestone:  1.8.1                                   
    Component:  packaging  |     Version:  1.6.1                                   
   Resolution:             |    Keywords:  binaries windows setuptools pycrypto-lib
Launchpad Bug:             |  
Changes (by zooko):

  * keywords:  windows setuptools pycrypto-lib => binaries windows
               setuptools pycrypto-lib
  * milestone:  soon (release n/a) => 1.8.1


 Since the newest version of !PyCrypto listed on
 http://pypi.python.org/pypi/pycrypto at the moment is 2.3, then we need to
 build bdist_egg's of !PyCrypto 2.3 for all platforms which we intend for
 people to be able to install Tahoe-LAFS v1.8.1 without having a C compiler
 and Python headers installed. (Note that the upstream maintainer of
 !PyCrypto will not provide binaries:
 https://bugs.launchpad.net/pycrypto/+bug/589511 .)

 Sadly, if we do all the work to build and host such binary eggs, and then
 a new version of !PyCrypto gets uploaded to !PyPI in source form, then our
 build scripts will immediately start refusing to use the !PyCrypto 2.3
 binaries that we built. Fixing this so that our build scripts would
 continue to use the !PyCrypto 2.3 binaries even if a newer version of
 !PyCrypto is known to them is the subject of #1233.

Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1065#comment:10>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage

More information about the tahoe-dev mailing list