[Grok-dev] Re: Python UK meeting and Django

Martijn Faassen faassen at startifact.com
Thu May 8 16:59:28 EDT 2008

Hi there,

Noah Gift wrote:
>     Yup, I'm game. The 1,000 file limit is pretty tough. A did a basic
>     test doing an install of ore.wsgiref, and ended up with 3000+ files
>     without including zcml.
>     My mini-strategy is to
>     * get easy_install zope.component
>     * get martian working
>     * implement custom traversal
>     * fork grok  :) doh!
>     After looking at the Datastore it may yet  be possible to do
>     object-based publishing by replacing persistence. I'll have to catch
>     up with you at Google I/O.
> Great.  Maybe the Grok/Zope experts can answer this question.  If you 
> had 1 month to live, and your life's goal was to make Grok work on 
> google app engine.  What would you do :)  


> Could it work.

Well, the 1000 file limit is tough. Martian should work easily enough, 
as it is plain Python (but for the zope.interface dependency, but you 
will need that too). zope.component is harder, but much of the stuff has 
Python implementations as well, so I'd try to get these working (the 
Zope on Jython project is doing this). After this, we should be able to 
establish grokcore.component.

You'd need to implement a container and model based on the app engine's 
data store. This is now possible with Grok trunk (and megrok.rdb uses this).

The question is how many dependencies the Zope publishing machinery has. 
  If that can be made working we'd be quite far along.

Anyway, it'd be good if we were a bit further along with our 
grokcore-ization. The more we push out into grokcore modules with 
hopefully controlled dependencies, the easier it would be to drop one or 
replace bits.

I'd aim for the intermediate goal of trying to make grokcore.component 
to work on the app-engine. That should give a good starting point for 
the rest.

Note that besides ore.wsgiref, there's also something Jim Fulton has 
been working on, zope.publisher.paste, that could be interesting to explore.



More information about the Grok-dev mailing list