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
Stephan Richter wrote at 2007-1-12 03:03 -0500:
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
On Thursday 11 January 2007 16:03, Dieter Maurer wrote:
Stephan Richter wrote at 2007-1-11 03:12 -0500:
...
If you are populating the CA before ZCML is fully parsed, then:
DO NOT POPULATE THE CA WHILE IMPORTING!!!
This is so bad on so many levels. Dieter, your problem is just one
On Thursday 11 January 2007 16:03, Dieter Maurer wrote:
Stephan Richter wrote at 2007-1-11 03:12 -0500:
...
If you are populating the CA before ZCML is fully parsed, then:
DO NOT POPULATE THE CA WHILE IMPORTING!!!
This is so bad on so many levels. Dieter, your problem is just one
Stephan Richter wrote at 2007-1-11 06:58 -0500:
On Thursday 11 January 2007 05:59, Chris Withers wrote:
Stephan Richter wrote:
If you are populating the CA before ZCML is fully parsed, then:
Why is the CA predicated on ZCML?!
Because that's how it works by default. Another way of saying this
Stephan Richter wrote at 2007-1-11 03:12 -0500:
...
If you are populating the CA before ZCML is fully parsed, then:
DO NOT POPULATE THE CA WHILE IMPORTING!!!
This is so bad on so many levels. Dieter, your problem is just one example.
Another is that unit tests have no chance to work reliably
On Wednesday 10 January 2007 05:45, Martijn Faassen wrote:
I'm a bit surprised why the huge [warning] is necessary. What I
understand you're saying is that you cannot use the component
architecture before it's done initializing. You also assert that you
need a registration to happen at Python
Stephan Richter wrote:
If you are populating the CA before ZCML is fully parsed, then:
Why is the CA predicated on ZCML?!
Chris
--
Simplistix - Content Management, Zope Python Consulting
- http://www.simplistix.co.uk
___
Zope maillist
On Thursday 11 January 2007 05:59, Chris Withers wrote:
Stephan Richter wrote:
If you are populating the CA before ZCML is fully parsed, then:
Why is the CA predicated on ZCML?!
Because that's how it works by default. Another way of saying this is:
Collect all registrations before executing
Stephan Richter wrote at 2007-1-11 03:12 -0500:
...
If you are populating the CA before ZCML is fully parsed, then:
DO NOT POPULATE THE CA WHILE IMPORTING!!!
This is so bad on so many levels. Dieter, your problem is just one example.
Another is that unit tests have no chance to work reliably
10 matches
Mail list logo
