Summary of messages to the zope-tests list.
Period Tue Jan 11 12:00:00 2011 UTC to Wed Jan 12 12:00:00 2011 UTC.
There were 107 messages: 8 from Zope Tests, 2 from buildbot at pov.lt, 22 from
buildbot at winbot.zope.org, 8 from ccomb at free.fr, 67 from jdriessen at
thehealthagency.com.
Test
Hello,
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
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
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
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
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
Am 11.01.2011, 22:44 Uhr, schrieb Tres Seaver tsea...@palladion.com:
Python 2.5 isn't even getting security fixes from Python devs now, which
means that Debian users are holding more risk than they know (I strongly
doubt the Debian packagers of Python are up for backporting all the
potential
