Well it tries to call only because the varial ISN'T a str :) If it's a string it behaves one way, else, it behaves another, and tries to call what it got. I imagine there's circumstances where this is used. I'll put something in the collector then, and we'll see where it goes. J.F. -----Original Message----- From: zope-bounces@zope.org [mailto:zope-bounces@zope.org] On Behalf Of Chris Withers Sent: September 3, 2007 02:55 To: Doyon, Jean-Francois Cc: zope@zope.org Subject: Re: [Zope] UTF encoding problem w/ ZPT's (No, not the usual :) Doyon, Jean-Francois wrote:
'user': <SpecialUser 'Anonymous User'>} TypeError: 'unicode' object is not callable
The problem is that zope.tales.tales.evaluate() tests for a str ... But, now, for unknown reasons, it's getting a unicode string.
...but even if it got an str, str's aren't callable either. Might be something to look at... cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk _______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )