I'd create a Product and put the monkey patching code anywhere in the product itself. The only thing that you probably can't change this way is security assertions, which are consulted early in the startup period and cannot effectively be changed afterwards. On Mon, 2003-09-01 at 12:59, Dennis Allison wrote:

I think I know how things are initialized, but I thought I'd verify my understanding by reading the documentation.

I couldn't find anything about initialization execution order in the documents even though I am sure I read it somewhere.

It's a question of where to put monkey patches for system code... A review of the archives didn't reveal much. If I want to change the behavior of, say, User.py by monkey patching, where's the right place to store them so they get executed in the right part of the initialization sequence?

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