Re: [Zope-dev] ConnectionStateError

2011-01-12 Thread Wichert Akkerman
On 1/12/11 14:34 , Godefroid Chapelle wrote: I also wonder what was the reason to deprecate ``zope.thread``. I see it was used by ``zope.component`` to hold thread-safe siteinfo. It has been obsoleted by http://docs.python.org/library/threading.html#threading.local Wichert.

Re: [Zope-dev] ConnectionStateError

2011-01-12 Thread Marius Gedminas
On Wed, Jan 12, 2011 at 02:34:13PM +0100, Godefroid Chapelle wrote: We have been experiencing some ConnectionStateError in a Zope 2 based application. Looking for info on the web makes me almost 100% sure that we have a bug in our application layer. I understand that I should look for

Re: [Zope-dev] ConnectionStateError

2011-01-12 Thread Dan Fairs
We have been experiencing some ConnectionStateError in a Zope 2 based application. Looking for info on the web makes me almost 100% sure that we have a bug in our application layer. I understand that I should look for persistent objects stored in module or class level variables (which

Re: [Zope-dev] ConnectionStateError

2011-01-12 Thread Hanno Schlichting
On Wed, Jan 12, 2011 at 2:34 PM, Godefroid Chapelle got...@bubblenet.be wrote: I understand that I should look for persistent objects stored in module or class level variables (which imply shared by threads and thus connections). Do not hesitate to tell me if this is a wrong explanation of the

Re: [Zope-dev] ConnectionStateError

2011-01-12 Thread Godefroid Chapelle
Le 12/01/11 17:06, Hanno Schlichting a écrit : On Wed, Jan 12, 2011 at 2:34 PM, Godefroid Chapellegot...@bubblenet.be wrote: I understand that I should look for persistent objects stored in module or class level variables (which imply shared by threads and thus connections). Do not hesitate