[Grok-dev] Grok emerging from the dependencies

Martijn Faassen faassen at startifact.com
Tue Apr 27 11:18:16 EDT 2010

Hi there,

Another task for those who'd like to help free Grok from dependencies:

Grok depends on zope.app.pagetemplate. When I remove this from the 
dependencies, viewlets fail to work. Figure out why? Something gets 
registered by zope.app.pagetemplate or a dependency of it that doesn't 
get registered and should be. What is it? Could it be moved within the 
ZTK? Let us know.

Grok depends on zope.app.publisher. When I remove this from the 
dependencies, there is a problem with XMLRPC. Could we move the XMLRPC 
code to zope.publisher perhaps?

It's easy enough to do this kind of research yourself:

Run bin/graph-depgraph. This produces a graph of the dependencies of 
Grok in SVG format. With firefox, go to parts/depgraph/grok/spec.svg to 
see it (zoom you a bit). You can now look at Grok's dependency graph.

Identify something that looks like it might be removable. Remove it from 
the configure.zcml. Remove it from setup.py. Possibly add the 
dependencies of the thing you're going to remove to both places. Re-run 

Run the tests. If 1 test fails (the exception view test) (the same test 
as what you get before making any changes), we're good. Check in with 
the dependency removed, repeat.

Of course, often enough you'll run into a snag. In that case you will 
need to start examining the package in question and possibly move things 
around in ZTK. But even just reporting your conclusions here is helpful. 
Let me know if you need any help.



More information about the Grok-dev mailing list