[Grok-dev] Re: Grok actions and grok.grok() cleanup

[Philipp von Weitershausen]

Martijn Faassen wrote:
>> The finalize method basically checked for unassociated tempates and
>> raises an error if it found any. I've turned this into a grokker as well
>> and gave it a very low priority (-1000) so it's executed after all other
>> grokkers.
> 
> A nice concept to use module grokkers for this. It's interesting how in 
> a year's time we evolved from a completely ad-hoc way to do this with 
> Grok to a separate, general system (Martian), and we continuously find 
> better ways to use this. We wouldn't have been able to design this last 
> year as we would've had no clue what we were doing, so it's very nice to 
> see that now we do. :)

Yes, I thought the same.

> [snip]
>> To summarize the visible changes for 3rd party code:
>>
>> * grok.grok() changed because of the configuration action dependency.
>> Use grok.tests.grok() (or wherever it will finally move) instead.
> 
> I'd advocate grok.testing.grok() for this, and you seem to agree, so it 
> looks like that will be the final location.

Yup. I'll do that then. Looks like when this is done, the branch can be 
merged, yes?


-- 
http://worldcookery.com -- Professional Zope documentation and training