On 3 December 2010 11:41, Chris Withers <ch...@simplistix.co.uk> wrote:
> I'd much prefer it to just be an "order of execution" thing, the nyou have
> total and flexible control. Combined with some logging about why something
> is as it is and you have your solution.

It's not always possible to control the order of execution. For
instance, with z3c.autoinclude, the order of inclusion is somewhat
random and although you can to some extend control the order via
explicit dependency includes, it's hard to work around 3rd party
packages that provide own overrides.

The problem with e.g. request layers as a means to prioritize is that
views adapt on (context, request) which makes it unfit for the purpose
if you have any views that specialize on the context interface.

Instead, priorities on the configuration level would be an easy
solution if you are trying to simply get a component to kick in.

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

Reply via email to