[Grok-dev] the notion of "next Grok"
cklinger at novareto.de
Thu Apr 16 04:57:52 EDT 2009
Jan-Wijbrand Kolman schrieb:
> On Wed, Apr 15, 2009 at 5:07 PM, Martijn Faassen <faassen at startifact.com> wrote:
>> Once we got it working for Grok we might want to push this down into the
>> Zope Toolkit, but I think Grok will have to pick up the ball here for
>> now, make it work for Grok. We can approach Plone developers on this
>> list too (or directly). I got nobody interested in this topic over on
> Just to note: I do find this interesting. I'm not sure though I
> already understand exactly what mr.developer accomplishes. I should
> play with first.
> I do know though that this testing of how well various packages (like
> for example the grokcore.* family) intergrate with Grok at a certain
> point in their development cycle is important - and curently somehwat
> inconvenient. Case in point are the heads-ups I sent to the list about
> failing tests.
I am not sure if i understand everything in detail but i created a
I looked a bit on the plone-coredev buildout which uses mr.developer for
the checkout´s of the various plone.packages.
As i said before i created a prototype which try´s to do the same for
grok, grokcore and martian packages.
Maybe someone can look on the buildout and provide some
feedback. You can find the grokcore-dev buildout here .
Please see this is a first attempt ;).
Here is README of the buildout:
Please Note: For this first prototype i used not the trunk of
grokcore.security because i get a version conflict
with the trunk of the other packgages.
This buildout generates a "out of the box" development
buildout for these grok packages:
This means that you find in the src directory the fresh checkout´s
of the trunk from the above packages.
The checkout´s are done with help of the buildout.recipe
mr.developer. For further information please look at the
pypi package of this package  or call the 'bin/develop help'
command which is created during buildout process, and should
show you some further information.
Starting the Grok instance with the wiki-application:
You can use the debug prompt with:
You can run the tests for a special package with:
./bin/test -s grokcore.formlib
If you want to run all tests you can run this command
And there are some commands for coverage-reports based
The ideas for this buildout is from the plone-coredev buildout .
So thanks for this...
More information about the Grok-dev