On 2007-08-09 17:21:57 +0200, Christian Zagrodnick <[EMAIL PROTECTED]> said:

On 2007-08-09 16:27:23 +0200, Hermann Himmelbauer <[EMAIL PROTECTED]> said:

Am Donnerstag, 9. August 2007 15:44 schrieb Hermann Himmelbauer:
After updating some z3c packages and changing some of my code, I recei
ve 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 somewhere in my code zalchemy is used, the TypeError emerges. It seems that recently there was a change to the zalchemy package (svn log):

r78682 | zagy | 2007-08-08 10:53:01 +0200 (Mi, 08 Aug 2007) | 1 line

using the threadlocal strategy of sqlalchemy instead of creating one en
gine per
thread. This allows connection pooling for instance.

I reverted zalchemy to an older version an all is well again.

Interesting. I wonder why this happens. I'll try to reproduce.

So it happend when the ZAlchemy engine was used as a local utility. Hermann, could you check if it works now?

Christian Zagrodnick

gocept gmbh & co. kg  ·  forsterstrasse 29 · 06112 halle/saale
www.gocept.com · fon. +49 345 12298894 · fax. +49 345 12298891

Zope3-users mailing list

Reply via email to