Opened at 2008-06-02T20:00:10Z
Closed at 2008-06-05T23:05:00Z
#438 closed defect (fixed)
get foolscap to declare its dependency on pyOpenSSL
Reported by: | zooko | Owned by: | somebody |
---|---|---|---|
Priority: | major | Milestone: | 1.1.0 |
Component: | packaging | Version: | 1.0.0 |
Keywords: | Cc: | ||
Launchpad Bug: |
Description
Per http://foolscap.lothar.com/trac/ticket/66 , if foolscap will declare its dependency on pyOpenSSL, then we can remove our declaration of our dependency on pyOpenSSL. This makes sense, for example if a future release of foolscap comes with a different SSL implementation or a completely different encryption protocol, Tahoe's dependency on pyOpenSSL will disappear, and the Tahoe setup.py itself should not need to know about that change.
If foolscap wants to preserve the possibility of a foolscap install which doesn't require pyOpenSSL and can't do secure mode, then it could declare the existence of a foolscap "extra" named "secure_connections" or something like that, and Tahoe could declare that it depends on "foolscap with secure_connections", like this:
install_requires.append("foolscap[secure_connections]")
Change History (1)
comment:1 Changed at 2008-06-05T23:05:00Z by warner
- Resolution set to fixed
- Status changed from new to closed
done, in yesterday's foolscap-0.2.8 release