[tahoe-lafs-trac-stream] [tahoe-lafs] #1383: foolscap 0.6.1 has no such extra feature 'secure_connections'
tahoe-lafs
trac at tahoe-lafs.org
Fri Apr 1 10:26:38 PDT 2011
#1383: foolscap 0.6.1 has no such extra feature 'secure_connections'
---------------------------+------------------------------------------------
Reporter: zooko | Owner: warner
Type: defect | Status: new
Priority: major | Milestone: undecided
Component: packaging | Version: 1.8.2
Resolution: | Keywords: setuptools foolscap pyOpenSSL
Launchpad Bug: |
---------------------------+------------------------------------------------
Comment (by zooko):
I remember that foolscap had a user or else a potential user who wanted to
use it with insecure connections. I also remember that foolscap has only
ever had two projects that depended on it: Tahoe-LAFS and ipython. I heard
the unsubstantiated rumor and that ipython has subsequently stopped using
foolscap and replaced it with ZeroMQ. (Although those are two different
classes of tool, but whatever.)
So, if ipython was the one user who wanted insecure connections, then
perhaps nobody would mind if foolscap gained a hard dependency on
pyOpenSSL.
Hm, it looks like the current release of ipython depends on foolscap and
also hard-depends on pyOpenSSL!
http://ipython.scipy.org/doc/rel-0.10.1/html/install/install.html
#dependencies-for-ipython-kernel-parallel-computing
Also note that gaining a hard dependency on pyOpenSSL doesn't preclude
foolscap from offering its "insecure connections" feature and doesn't
preclude people from using it.
So anyway, I would like it if Brian would make pyOpenSSL be a hard
dependency of foolscap. This would simplify matters as far as dependency
management goes, and doesn't seem to cause much harm. People who aren't
using setuptools/easy_install/pip/virtualenv don't even notice whether or
not foolscap declares pyOpenSSL to be a dependency.
--
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1383#comment:6>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list