On Thursday 11 January 2007 16:10, Dieter Maurer wrote: > I can see that such a strategy may be helpful when one wants to > resolve conflicts in some way. However, I do not see > why is should be necessary for registration that are not expected > to conflict.
Going into some detail. If imports have registration side-effects, then a test suite can never cleanly tear down. After each test suite run, the entire component architecture registry is cleared. That would also clear all your regstrations made during import time. There are strategies to deal with this, see zope.security package, but it is tedious and takes time to get fully right. BTW, you can use the "--repeat/-N" option to run tests multiple times. This will show you, if you setup and teardown correctly. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training _______________________________________________ Zope-Dev maillist - [email protected] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
