[Grok-dev] Re: issueing a warning,
not an error when template files are not associated
janwijbrand at gmail.com
Wed Nov 14 06:14:17 EST 2007
Philipp von Weitershausen wrote:
> Jan-Wijbrand Kolman wrote:
>> Somehow this happens to me a lot; I guess I frequently copy or move or
>> create templates while developing, without (yet) having a view class
>> for it. Then I find Zope not starting and thus I need to somehow
>> disable the template, by renaming it for example (it used to be even
>> harder: you had to move it out of the dir, or prefix the filename with
>> a dot, because Grok would choke on unrecognized names).
>> Question: what about just issueing a UserWarning for any template that
>> could not be associated, instead just for the files with an
>> unrecognized filename?
I'm working on it right now.
>> So, another question: is it possible to raise the GrokError (or the
>> afformentiond UserWarning) about unassociated templates after the
>> grokkking process for a package is completed?
> Perhaps. We'd have to introduce a new type of grokker, though. And we'll
> have to introduce a template registry registry (sic!) so that two
> modules can share the same template registry.
Yeah, this feature is a little more involved indeed. I'm not sure how to
implement it actually. What do you mean with a new type of grokker?
More information about the Grok-dev