[Zope-dev] zope.app.publication dependencies (volunteersneeded!)
faassen at startifact.com
Fri May 15 07:30:32 EDT 2009
Michael Howitz wrote:
> Am 14.05.2009 um 15:02 schrieb Martijn Faassen:
>> Is this replacement compatible with zope.formlib's namedtemplate
>> mechanism? Will anything break?
> No it is not compatible. So I think it's a bad idea.
Ah, all right, glad we agree.
> Breaking the
> dependency between zope.app.publication and zope.app.exception by
> moving the ISystemErrorView interface and maybe the class which
> implements it to zope.browser would be better. I'll look into it at
>> I understand. Why not move the namedtemplate mechanism somewhere else
>> entirely, though? This way we'd not introduce new code. The
>> namedtemplate code itself only seems to depend on zope.traversing, but
>> that doesn't sound like a good home. The tests depend on
>> zope.app.pagetemplate, so perhaps it should move there? This is
>> still a
>> dependency of zope.app.exception anyway, and it itself doesn't
>> appear to
>> depend on zope.formlib.
> Nice idea. I'll look into it.
Cool. It would seem to make sense that the named template mechanism is
bundled along with the page template library anyway (instead of the form
library). zope.formlib currently depends on zope.app.pagetemplate too so
we could easily leave a backwards compatibility import in place.
zope.app.pagetemplate might be worth our further attention later, but
this at least would clean up a bit more mess as a first step.
More information about the Zope-Dev