Fred Drake wrote at 2007-1-10 17:30 -0500:
On 1/10/07, Dieter Maurer [EMAIL PROTECTED] wrote:
*It* must be informed whenever it is used in a different thread.
Perhaps it could use some thread-local data to keep track of this?
threading.local comes to mind.
This is a nice idea but in this case
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?!
It's not. And Stephan's Collect all registrations before executing
them! isn't actually necessary either (it's just necessary for conflict
Martijn Faassen wrote at 2007-1-10 11:45 +0100:
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.
The warning comes from bad experience.
I have tested my
Philipp von Weitershausen wrote at 2007-1-10 15:40 +0100:
...
Things changed a bit after Zope 2.8/X3 3.0. Nowadays, the Component
Architecture doesn't need any setup anymore and you can do registrations
on import.
Very good!
I'd still recommend against that.
Why?
...
That's because Five
On 1/10/07, Dieter Maurer [EMAIL PROTECTED] wrote:
*It* must be informed whenever it is used in a different thread.
Perhaps it could use some thread-local data to keep track of this?
threading.local comes to mind.
-Fred
--
Fred L. Drake, Jr.fdrake at gmail.com
Every sin is the result
Dieter Maurer wrote:
I tried to use Zope3 events to get informed when requests start and end.
One of our modules (the interface module to jpype) requires such
a notification for reliable work. Therefore, it tried to register
the corresponding subscriptions on import of this module.
Dieter Maurer wrote:
I tried to use Zope3 events to get informed when requests start and end.
One of our modules (the interface module to jpype) requires such
a notification for reliable work. Therefore, it tried to register
the corresponding subscriptions on import of this module.
That is an
Martijn Faassen wrote at 2007-1-10 11:45 +0100:
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.
The warning comes from bad experience.
I have tested my
Philipp von Weitershausen wrote at 2007-1-10 15:40 +0100:
...
Things changed a bit after Zope 2.8/X3 3.0. Nowadays, the Component
Architecture doesn't need any setup anymore and you can do registrations
on import.
Very good!
I'd still recommend against that.
Why?
...
That's because Five
On 1/10/07, Dieter Maurer [EMAIL PROTECTED] wrote:
*It* must be informed whenever it is used in a different thread.
Perhaps it could use some thread-local data to keep track of this?
threading.local comes to mind.
-Fred
--
Fred L. Drake, Jr.fdrake at gmail.com
Every sin is the result
10 matches
Mail list logo
