[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:  closed
     Priority:  major               |  Milestone:  1.11.0
    Component:  dev-infrastructure  |    Version:  1.8.0
   Resolution:  fixed               |   Keywords:  setuptools test docs
Launchpad Bug:                      |
------------------------------------+----------------------------------

Comment (by gdt):

 I came back to this while reviewing the pkgsrc package.  While it is
 certainly ok to *recommend* using a virtualenv, it is not ok to say that
 tahoe working properly outside of a virtualenv is beyond the
 specification.

 Certainly it is fair to expect that the installed versions of dependencies
 are ok.  It's really the separation of the installed, likely previous
 working tahoe, and the being-built next version for testing that matters.
 It is normal for packaging systems to build and test not installed
 versions.

 Do people think this problem is resolved, for running tests in a build dir
 while a previous version is in site packages?  Or is this just tahoe
 adopting an usual definition of correctness?  (Really asking; I have no
 idea.)

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1258#comment:32>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage