missing import when .buildout/default.cfg puts eggs outside ~/.buildout

Bug #299400 reported by Russ Ferriday on 2008-11-18
Affects Status Importance Assigned to Milestone

Bug Description

ZODB 3.8.1 tag
Python 2.4.4

Problem occurs when I use non-standard location for my downloads and eggs...

$ cat ~/.buildout/default.cfg
download-directory = /opt/zope/stashes/downloads
eggs-directory = /opt/zope/stashes/eggs

This seems to conflict with the install process that seems to expect eggs here:

$ svn co svn://svn.zope.org/repos/main/ZODB/tags/3.8.1 ZODB
$ cd ZODB
$ /opt/zope/python244/bin/python bootstrap.py
$ bin/buildout
$ bin/test -v
Traceback (most recent call last):
  File "/opt/zope/instances/ZODB/bin/test", line 18, in ?
    import zope.testing.testrunner
  File "/Users/russ/.buildout/eggs/zope.testing-3.7.1-py2.4.egg/zope/testing/testrunner/__init__.py", line 23, in ?
  File "/Users/russ/.buildout/eggs/zope.testing-3.7.1-py2.4.egg/zope/testing/testrunner/interfaces.py", line 23, in ?
ImportError: No module named interface

Simple Workaround:

Make the default.cfg approximate what the buildout expects:

$ cat ~/.buildout/default.cfg
download-directory = /Users/russ/.buildout/download
eggs-directory = /Users/russ/.buildout/eggs

$ bin/test -v
Running tests at level 1
Running zope.testing.testrunner.layer.UnitTests tests:
  Set up zope.testing.testrunner.layer.UnitTests in 0.000 seconds.
  Ran 3023 tests with 0 failures and 0 errors in 8 minutes 2.798 seconds.
Tearing down left over layers:
  Tear down zope.testing.testrunner.layer.UnitTests in 0.000 seconds.

Russ Ferriday (russf) wrote :

Just to clarify...

At the time of the failed test, the directory


does not exist -- the eggs are in /opt/zope/stashes/eggs


Jim Fulton (jim-zope) wrote :

This sounds like it might be a zc.buildout bug, although buildout has no "download-directory".

affects: zodb → zc.buildout
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers