Opened at 2011-08-01T23:47:02Z
Closed at 2016-03-27T18:34:53Z
#1464 closed defect (fixed)
stronger isolation between the Python libraries imported by build steps and those used by buildbot
Reported by: | davidsarah | Owned by: | somebody |
---|---|---|---|
Priority: | major | Milestone: | 1.11.0 |
Component: | dev-infrastructure | Version: | 1.8.2 |
Keywords: | buildbot twisted pywin32 | Cc: | |
Launchpad Bug: |
Description (last modified by warner)
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.
Change History (3)
comment:1 Changed at 2011-08-01T23:47:56Z by davidsarah
- Description modified (diff)
comment:2 Changed at 2013-05-03T21:59:42Z by zooko
comment:3 Changed at 2016-03-27T18:34:53Z by warner
- Description modified (diff)
- Milestone changed from undecided to 1.11.0
- Resolution set to fixed
- Status changed from new to closed
We now use tox and virtualenv, which gives us the isolation we need.
Note: See
TracTickets for help on using
tickets.
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"