Opened at 2012-07-10T22:58:09Z
Last modified at 2020-11-30T13:46:08Z
#1792 closed defect
make Tahoe-LAFS work under PyPy — at Version 2
Reported by: | davidsarah | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | eventually |
Component: | packaging | Version: | 1.9.2 |
Keywords: | pypy cpyext packaging pycryptopp | Cc: | tahoe-lafs.org@… |
Launchpad Bug: |
Description (last modified by hawkowl)
If I remember correctly, the main obstacle was extension modules. Current PyPy? supports extension modules compiled for CPython, but is not 100% compatible with the CPython extension API.
Change History (2)
comment:1 Changed at 2012-07-11T21:31:16Z by davidsarah
comment:2 Changed at 2015-07-29T04:10:16Z by hawkowl
- Description modified (diff)
From an IRC discussion about why it doesn't work (pycryptopp), I decided to look at Cryptography and pynacl, and what uses pycryptopp in tahoe.
- ed25519 is supported by pynacl.
- AES is supported by Cryptography.
- RSA keys (in many formats) are supported by Cryptography.
- SHA256 hashes are supported by Cryptography.
Zooko mentioned that Cryptography has a hard dependency on OpenSSL (which he rightfully dislikes) but my unqualified self thinks that it might not be so bad. Worth a shot, maybe? I have (some) time on Tuesday's PyCon? AU sprint session to maybe take a hack on it, if the maintainers don't find the current-hard-dep on OpenSSL a dealbreaker.
fijal wrote in #pypy: