Comment 4 for bug 286288

Revision history for this message
Thomas Lotze (tlotze) wrote :

I'm using a self-compiled Python 2.5.1 and a virtualenv created from it. In the virtualenv, I've installed grokproject 0.9 (using easy_install, which pulled it from PyPI). I then created a fresh Grok project which went fine. Using the Python executable from the virtualenv, I can run bootstrap.py fine. Using the original Python executable from whose installation I created the virtualenv, I can't. I'm also sure that I used the bootstrap.py put in the fresh project directory by grokproject in both cases; see the transcript below.

Doing something similar without grokproject works, though: If I create an empty directory with a minimal buildout.cfg, copy the latest tagged bootstrap.py to it and run the two Pythons on it in the same order, everything works as expected.

thomas@krusty:~/tmp$ grokproject foo
Enter user (Name of an initial administrator user): admin
Enter passwd (Password for the initial administrator user):
Downloading info about versions...
Creating directory ./foo
Downloading zc.buildout...
Invoking zc.buildout...
Develop: '/home/thomas/tmp/foo/.'
Installing eggbasket.

thomas@krusty:~/tmp$ cd foo/

thomas@krusty:~/tmp/foo$ python bootstrap.py
Develop: '/home/thomas/tmp/foo/.'
Installing 'z3c.recipe.eggbasket'.
We have the distribution that satisfies 'z3c.recipe.eggbasket==0.4.0'.
Getting required 'zc.recipe.egg==1.1.0b1'
We have the distribution that satisfies 'zc.recipe.egg==1.1.0b1'.
Updating eggbasket.
Now you can run 'bin/buildout'

thomas@krusty:~/tmp/foo$ /opt/Python-2.5/bin/python bootstrap.py
Downloading http://pypi.python.org/packages/2.5/s/setuptools/setuptools-0.6c9-py2.5.egg
Generated script '/home/thomas/tmp/foo/bin/buildout'.
Develop: '/home/thomas/tmp/foo/.'
Traceback (most recent call last):
  File "/tmp/tmp07z1jx", line 5, in <module>
    import os, setuptools
ImportError: No module named setuptools
While:
  Installing.
  Processing develop directory '/home/thomas/tmp/foo/.'.

An internal error occured due to a bug in either zc.buildout or in a
recipe being used:
Traceback (most recent call last):
  File "/tmp/tmplSbcEb/zc.buildout-1.1.1-py2.5.egg/zc/buildout/buildout.py", line 1477, in main
  File "/tmp/tmplSbcEb/zc.buildout-1.1.1-py2.5.egg/zc/buildout/buildout.py", line 324, in install
  File "/tmp/tmplSbcEb/zc.buildout-1.1.1-py2.5.egg/zc/buildout/buildout.py", line 556, in _develop
  File "/tmp/tmplSbcEb/zc.buildout-1.1.1-py2.5.egg/zc/buildout/easy_install.py", line 866, in develop
AssertionError