On Aug 10, 2007, at 2:30 AM, Christian Theune wrote:
Am Donnerstag, den 09.08.2007, 09:52 -0400 schrieb Gary Poster:
You probably need to find out what the object is for anyone to have a
chance of helping.
I usually just put a pdb in the ZODB that is triggered if there's an
error here, and th
Am Donnerstag, den 09.08.2007, 09:52 -0400 schrieb Gary Poster:
> You probably need to find out what the object is for anyone to have a
> chance of helping.
>
> I usually just put a pdb in the ZODB that is triggered if there's an
> error here, and then start poking around. Using the postmorte
Hermann Himmelbauer wrote:
Once again it proves that updating only makes sense if an update is really
necessary... ;-)
Or if your express intent is to pay off some version debt.
--
Benji York
Senior Software Engineer
Zope Corporation
___
Zope3-users m
Am Donnerstag, 9. August 2007 15:44 schrieb Hermann Himmelbauer:
> Hi,
> After updating some z3c packages and changing some of my code, I receive a
> very strange traceback from Zope3:
Ah, after fiddling around I found out that the "svn update" of the zalchemy
package resulted in this error. If s
You probably need to find out what the object is for anyone to have a
chance of helping.
I usually just put a pdb in the ZODB that is triggered if there's an
error here, and then start poking around. Using the postmortem debug
publisher might work too, but it has caused enough problems for
Hi,
After updating some z3c packages and changing some of my code, I receive a
very strange traceback from Zope3:
--
Traceback (most recent call last):
File "/local/home/dusty/Zope-3.4.0b1/lib/python/zope/publisher/publish.py",
line 138, in publish
publication.afterCall(req
