[tahoe-lafs-trac-stream] [tahoe-lafs] #1383: foolscap 0.6.1 has no such extra feature 'secure_connections'

[tahoe-lafs]

#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):

 Replying to [comment:1 davidsarah]:
 > > 2. We could hack the fork of setuptools which is bundled into the
 Tahoe-LAFS source tree (sometimes called "zetuptoolz") so that it doesn't
 treat a missing extra as a fatal error. The theory being that if the
 package doesn't declare an extra then probably it actually has that extra
 but didn't declare it.
 >
 > Well, if the installed package doesn't satisfy the dependency (for
 whatever reason), then setuptools should try to download a version that
 does. Even if the latter has the same version ''number'', it might not
 have the same packaging error.

 I agree that would be better behavior for zetuptoolz than my proposed
 behavior for zetuptoolz, and I also agree that I really don't want to try
 to improve zetuptoolz's behavior. If we had a good way to unit-test
 zetuptoolz's behavior on our buildbot then maybe, but currently I think I
 would first have to improve the ways that our buildbot unit-tests
 zetuptoolz's behavior and then improve zetuptoolz's behavior, and that's a
 lot of work for this one issue. I no longer think of setuptools/zetuptoolz
 as a good long-term investment so I no longer think that all of that work
 would pay for itself again in more and more future issues.

 That said, I don't see any ''other'' solution to this one issue than the
 ones we've listed here...

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1383#comment:5>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage