[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2193: pyOpenSSL 0.14 pulls in a bunch of new dependencies

[Tahoe-LAFS]

#2193: pyOpenSSL 0.14 pulls in a bunch of new dependencies
-------------------------+-------------------------------------------------
     Reporter:  daira    |      Owner:
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:  undecided
    Component:           |    Version:  1.10.0
  packaging              |   Keywords:  packaging setuptools pyopenssl
   Resolution:           |  cryptography six cffi pycparser
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by dstufft):

 For what it's worth, I'm both a cryptography developer (kind of, I'm
 probably the least active one of us) and a PyPA developer. I also have
 PyNaCl and bcrypt which also use the cffi backends. cffi has some pitfalls
 with packaging right now, however they are being worked on both on the
 cffi side with work to remove the implicit compile stuff, in the project
 themselves with work arounds, and in the packaging tools to better handle
 binary dependencies in general.

 What tahoe-lafs decides to do with it's dependencies will affect y'all far
 more than it affects me, but I would suggest that pinning to an old
 release of pyOpenSSL will end up causing you more grief in the long run. I
 concur with that you should either get rid of it or adopt to the newer
 style of things.

 I also think it'd probably be reasonable for cryptography.io to look to
 handle more of what tahoe needs from a crypto library too if you're all
 interested in that. We have very stringent requirements for what gets
 committed to our code base as far as code quality, test coverage,
 documentation etc goes and we have goals of being somewhat of a standard
 library of crypto :).

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2193#comment:17>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage