[tahoe-lafs-trac-stream] [tahoe-lafs] #1258: having Tahoe or any dependency installed in site-packages (or any other shared directory) can cause us to run or test the wrong code

[tahoe-lafs]

#1258: having Tahoe or any dependency installed in site-packages (or any other
shared directory) can cause us to run or test the wrong code
------------------------------------+---------------------------------------
     Reporter:  davidsarah          |       Owner:  davidsarah          
         Type:  defect              |      Status:  new                 
     Priority:  major               |   Milestone:  1.9.0               
    Component:  dev-infrastructure  |     Version:  1.8.0               
   Resolution:                      |    Keywords:  setuptools test docs
Launchpad Bug:                      |  
------------------------------------+---------------------------------------

Comment (by davidsarah):

 Replying to [comment:26 zooko]:
 > David-Sarah: I would give +1 to
 [20110101110141-93fa1-3557bc2136f970fae05c1d20e336c32fec8e3d6d] if we put
 back the {{{pkg_resources.require()}}} and add code to abort with a
 specific error message if the answer provided by
 {{{pkg_resources.require()}}} differs from the one detected by importing
 and inspecting the module.
 >
 > This would satisfy my current uncertainty (re comment:24), would be in
 keeping with the intent to detect this problem in 1.8.2, would fail-safe,
 and would not cause any problem in the case that {{{pkg_resources}}} was
 behaving correctly. What do you think?

 +1. This check might have to be disabled for a frozen executable (but in
 that case the dependencies should also have been frozen at build time, so
 I don't think the check is needed in that case).

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