[Grok-dev] problems with the philikon-eggification branch

Martijn Faassen faassen at startifact.com
Mon Apr 23 15:37:07 EDT 2007

Hi there,

I have been looking at the philikon-eggification branch, and I'm ranning 
into a few snags.

The first problem is that the bin/instance script for some reason ends 
up with only a fraction of the eggs it should be:


import sys
sys.path[0:0] = [

The test runner does end up with a much larger set of eggs. Hm, it looks 
like I just fixed this by adding the following:

eggs = grok

to the [instance] section. What is going on here? [app] already lists 
these and [instance] refers to app. I'm not familiar with the 
zc.zope3recipes recipe, but you'd think it would use the eggs dependency 
from [app].

The second problem is that when I do bin/test, I get the following error:

Traceback (most recent call last):
   File "/home/faassen/buildout/grok-eggs/src/grok/__init__.py", line 
18, in ?
     from zope.component import adapts
line 19, in ?
line 1, in ?
line 20, in ?
line 21, in ?
undefined symbol: PyUnicodeUCS4_AsEncodedString

I've seen this one before. This is because the zope.proxy egg has been 
uploaded as binary, and this leads to problems outside of Windows. My 
Python has been compiled with UCS2 and the Python that was used to 
compile the egg was set to UCS4, and this is incompatible. Jim already 
warned against doing this for Linux eggs and uploading sources only 
instead, and I will take this up on the Zope 3 dev mailing list.



More information about the Grok-dev mailing list