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

Philipp von Weitershausen philipp at weitershausen.de
Tue Apr 24 09:44:41 EDT 2007

On 24 Apr 2007, at 15:32 , Martijn Faassen wrote:
> Philipp von Weitershausen wrote:
>> Martijn Faassen wrote:
>>>> Or your buildout didn't pull in the zope.app.zcmlfiles egg,  
>>>> which would be strange because it works for me.
>>> There indeed does not appear to be a zope.app.zcmlfiles egg  
>>> present. Did you try running the buildout from scratch? It's  
>>> possible the egg dependencies got changed at some stage?
>> Yeah, probably some time before the 3.4.0a1 eggs were built and  
>> uploaded recently.
>> It's actually a good sign that Grok doesn't have to depend on  
>> neither zope.app.twisted, zope.app.securitypolicy and  
>> zope.app.zcmlfiles (those three were needed to get the egg-based  
>> buildout going again). I've amended buildout.cfg to install those.  
>> The egg buildout should work again now.
> So if we have to install those to make Grok work, why do you say  
> Grok doesn't have to depend on them?

We have to install them to make Grok work in this particular  
deployment scheme. I'm using zope.paste + paste.deploy for NudgeNudge  
and therefore don't need zope.app.server or zope.app.twisted.

> Some comments:
> * I needed to list 'eggs' in instance as well. evidently you didn't  
> need to do that. What's up with that?

What do you mean?

> * there is a zc.twisted egg now that I included in the setup.py You  
> didn't seem to need that, so that means you have a twisted already  
> on your PYTHONPATH?

No. The zope.app.twisted egg contains both the zope.app.twisted  
package and twisted.

More information about the Grok-dev mailing list