Hi there,

Michael Howitz wrote:
> z3c.template is used there instead of zope.formlib.
> I can merge this branch in the next days and cut a release.

I'm worried by the amount of *new* code that is pulled in just to reduce 
a dependency. Making this change would pull in *more* dependencies, not 

Not only do we pull in z3c.template, this package also pulls in 
z3c.ptcompat, which in turn needs extras to actually work. As Roger says 
this is a compatibility layer, and that isn't pretty either.

We shouldn't pull in new code to reduce dependencies. Any new code added 
into the Zope Toolkit and that shouldn't be done without a discussion 
(and not done as a minor dependency refactoring).

zope.app.exception defines views that pull in standard_macros. I'm not 
sure the Zope Toolkit should be concerned with views at all at this 
stage. I'd like to consider moving the whole page template story off 
into its own area at some point that is not core to the Toolkit, so it's 
easy to use other templating systems.

The only reason zope.app.publication appears to be depending on 
zope.app.exception is because it needs ISystemErrorView. It's used once 
somewhere deep within complex exception handling code.

I propose we move ISystemErrorView from zope.app.exception into 
zope.browser, hopefully cutting zope.app.exception out of the dependency 
tree entirely.



Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to