stronger isolation between the Python libraries imported by build steps and those used by buildbot #1464

New Issue

tahoe-lafs · 2011-08-01T23:47:02Z

davidsarah commented

2011-08-01 23:47:02 +00:00

buildbot uses some of the same Python libraries as Tahoe, for example Twisted and pywin32. This creates problems for build steps that want to test what happens when those libraries are not installed, or when a version that is not compatible with buildbot is installed.

#1334 is a special case of this problem, and it also affects #1346.

Possible solutions include using virtualenv, or setting up PYTHONPATH differently for buildbot and for the code under test.

buildbot uses some of the same Python libraries as Tahoe, for example Twisted and pywin32. This creates problems for build steps that want to test what happens when those libraries are not installed, or when a version that is not compatible with buildbot is installed. #1334 is a special case of this problem, and it also affects #1346. Possible solutions include using virtualenv, or setting up PYTHONPATH differently for buildbot and for the code under test.

tahoe-lafs added the

labels 2011-08-01 23:47:02 +00:00

tahoe-lafs added this to the undecided milestone 2011-08-01 23:47:02 +00:00

zooko commented

2013-05-03 21:59:42 +00:00

Something else that might help with this would be using exocet instead of the builtin Python module loader: #1443 "use exocet instead of the builtin Python module loader"