[tahoe-lafs-trac-stream] [Tahoe-LAFS] #1792: make Tahoe-LAFS work under PyPy

[Tahoe-LAFS]

#1792: make Tahoe-LAFS work under PyPy
----------------------------+----------------------------------------------
     Reporter:  davidsarah  |      Owner:
         Type:  defect      |     Status:  new
     Priority:  normal      |  Milestone:  eventually
    Component:  packaging   |    Version:  1.9.2
   Resolution:              |   Keywords:  pypy cpyext packaging pycryptopp
Launchpad Bug:              |
----------------------------+----------------------------------------------

Comment (by warner):

 Foolscap depends upon OpenSSL too, and even though we're planning on
 replacing Foolscap (#510), for backwards compatibility we'll probably need
 it for quite a while yet. Also when we replace it, we may wind up wanting
 TLS-protected HTTP instead of just plain HTTP (to maintain privacy of
 which shares you're fetching), which might be another thing that depends
 upon OpenSSL. I'm not a fan of OpenSSL either, but I don't think depending
 upon it would be the worst direction to go. Maybe our policy could be to
 use pynacl for new features, and migrate old ones from pycryptopp to
 cryptography?

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