On 3/14/07, Baiju M <[EMAIL PROTECTED]> wrote:
I think you added (by mistake?) this link instead:
http://pyre.third-bit.com/blog/archives/863.html
Whoops, indeed, that's not the right one. Blame late night
inattention, brought on by a better half asking when I was going to be
done. ;)
I found
Tres Seaver wrote:
Module ZODB.Connection, line 814, in _setstate_noncurrent
AssertionError
This is on Zope 2.9.4.
Any ideas?
Have you looked at the code?
Yup, sure did.
I can only guess that _setstate_noncurrent is called when the mvcc code
decides it needs data from state that isn't the
Summary of messages to the zope-tests list.
Period Tue Mar 13 12:00:00 2007 UTC to Wed Mar 14 12:00:00 2007 UTC.
There were 5 messages: 5 from Zope Unit Tests.
Tests passed OK
---
Subject: OK : Zope-2.7 Python-2.3.6 : Linux
From: Zope Unit Tests
Date: Tue Mar 13 21:54:48 EDT 2007
URL
I recently file this bug http://www.zope.org/Collectors/Zope/2290 however an
error seems to have kept email notifications from being sent out. The issue
is that DateTimeZone.py has the wrong changeover points for DST for the USA
in it. This is used for all the DateTime zone conversions in DateTi
On Mar 14, 2007, at 5:16 PM, William Heymann wrote:
I recently file this bug http://www.zope.org/Collectors/Zope/2290
however an
error seems to have kept email notifications from being sent out.
The issue
is that DateTimeZone.py has the wrong changeover points for DST for
the USA
in it. Th
--On 14. März 2007 15:16:05 -0600 William Heymann <[EMAIL PROTECTED]>
wrote:
I recently file this bug http://www.zope.org/Collectors/Zope/2290 however
an error seems to have kept email notifications from being sent out. The
issue is that DateTimeZone.py has the wrong changeover points for
