[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 trac at tahoe-lafs.org
Thu Jan 20 20:41:58 UTC 2011


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

 Thise check is causing several failures on the buildslaves. Arguably they
 are false positives from a user's perspective (because we ''are''
 importing acceptable versions of the dependencies in these cases), even
 though they indicate that pkg_resources is deeply confused.

 I propose that we should only perform this cross-check when one of the
 version-checking options is used ({{{bin/tahoe --version}}}, {{{--version-
 and-path}}} or {{{--debug-version-and-path}}}), or when {{{setup.py
 test}}} or {{{setup.py trial}}} is used. In the latter case, it should not
 stop us running tests.

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


More information about the tahoe-lafs-trac-stream mailing list