On 28/09/2010 12:55, Tres Seaver wrote:
On 09/28/2010 03:36 AM, Chris Withers wrote:
On 28/09/2010 00:12, Marius Gedminas wrote:
--- ./OFS/History.py.orig 2010-09-28 02:11:56.535745440 +0300
+++ ./OFS/History.py2010-09-28 02:12:00.043764683 +0300
@@ -151,6 +151,9 @@
On Tue, Sep 28, 2010 at 3:12 AM, Adam GROSZER agros...@gmail.com wrote:
Hello Alan,
They pass since the summit, when Jim fixed the windows failures.
http://winbot.zope.org/builders
Actually, they passed since I fixed a couple of ZEO cache management
bugs on August 30 and September 7. What's
http://pypi.python.org/pypi/ZODB3/3.9.7
This was mainly motivated by the Python 2.7 fix, since we'd previously
made Python 2.7 windows binaries available.
Jim
--
Jim Fulton
___
For more information about ZODB, see the ZODB Wiki:
Hello,
I keep getting this traceback with ZODB 3.9.4.
Traceback (most recent call last):
File
c:\users\nitro\.buildout\eggs\zope.publisher-3.12.3-py2.6.egg\zope\publi
sher\publish.py, line 130, in publish
obj = publication.getApplication(request)
File
Am 29.09.2010, 00:34 Uhr, schrieb Jim Fulton j...@zope.com:
Is this a bug in ZODB?
It appears so. Are you specifying a pool timeout?
I don't set a timeout anywhere specifically. Maybe there is one a default
one buried in grok/ztk, but I couldn't find anything on quick inspection.
However,
On Tue, Sep 28, 2010 at 6:42 PM, Matthias ni...@dr-code.org wrote:
Am 29.09.2010, 00:34 Uhr, schrieb Jim Fulton j...@zope.com:
Is this a bug in ZODB?
It appears so. Are you specifying a pool timeout?
I don't set a timeout anywhere specifically. Maybe there is one a default
one buried in
