1. Tarek Ziadé
  2. distribute
  3. Issues
Issue #97 new

bootstrap.py crashes with MacPorts Python 2.5

Tim Molendijk
created an issue

I get the following error while running bootstrap.py:


!Downloading http://pypi.python.org/packages/source/d/distribute/distribute-0.6.8.tar.gz

Extracting in /var/folders/eD/eDj9etIFFjWoXRTh7oARZE+++TI/-Tmp-/tmpxoKx Now working in /var/folders/eD/eDj9etIFFjWoXRTh7oARZE+++TI/-Tmp-/tmpxoKx/distribute-0.6.8 Building a Distribute egg in /var/folders/eD/eDj9etIFFjWoXRTh7oARZE+++TI/-Tmp-/tmpqZE283 /var/folders/eD/eDj9etIFFjWoXRTh7oARZE+++TI/-Tmp-/tmpqZE283/distribute-0.6.8-py2.5.egg 'import site' failed; use -v for traceback Traceback (most recent call last): File "<string>", line 1, in <module> zipimport.ZipImportError: can't decompress data; zlib not available Traceback (most recent call last): File "/usr/local/share/buildout/bootstrap.py", line 107, in <module> ) == 0 AssertionError }}}

I'm running Python 2.5 from MacPorts (at {{{/opt/local/Library/Frameworks/Python.framework/Versions/2.5/bin/python}}}), with the following packages installed: zlib, libzzip, py25-zlib.

Comments (6)

  1. Tarek Ziadé repo owner

    Are you running a buildout ?

    It seems that your Python doesn't have zlib support, which is required for zipped eggs (and for a zc.buildout environment therefore).

    Can you install it and retry ?

  2. Tim Molendijk reporter

    Alright, made some progress. The problem is with running bootstrap.py with a Python 2.5 instance from MacPorts. For some reason it is not finding site.py, which results in zlib not ending up in python path, which results in the reported error. By the way, this issue is also present in zc.buildout's native bootstrap.py.

  3. Tarek Ziadé repo owner

    Steve I think it's a side effect of site.py breaking


    "'import site' failed; use -v for traceback" means that the python instance triggered to build the egg is not properly initialized.

    What you can do to trace the problem is modify "_python_cmd" in distribute_setup.py, and add just before the spawn call a "-v" as a first option.

      args.insert(0, '-v')

    This should display the traceback occurring during the init phase

  4. Log in to comment