[Grok-dev] Re: Using martian to load schemata

[Martin Aspeli]

Martijn Faassen <faassen <at> startifact.com> writes:

> This has absolutely nothing to do with Martian, just with the way 
> configuration works in Zope 3. If you are going to define your schema at 
> configuration time (or run time) and want to *use* them during import 
> time (as grok.Fields or formlib in general actually does), i.e. *before* 
> configuration, you'll have this problem.

Yeah, I understand. I can just imaging myself wanting to use things like
utilities and adapters to write grokkers, thus getting into such a chicken
and egg problem. Maybe it's not a common need, though.

> In the rdb case we're not even using Martian to define the schema, we 
> just call a function to get it, defining the schema during run time.
> 
> You can use Zope 3 components in zope.configuration actions, you just 
> need to get the order right.

Right. I'll pick a really high number. ;-)