l see where it goes.
J.F.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 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:
Doyon, Jean-Francois wrote:
'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 somet
ki [mailto:[EMAIL PROTECTED]
Sent: August 30, 2007 08:49
To: Doyon, Jean-Francois
Cc: Chris Withers; zope@zope.org
Subject: Re: [Zope] UTF encoding problem w/ ZPT's (No, not the usual :)
> As for subversion, I took great care to make sure everything was utf-8
> on the FS, during de
> As for subversion, I took great care to make sure everything was utf-8
> on the FS, during development, and I know Subersion uses utf-8
> internally, so I'm not sure what it would change it to. Once checked
> back out, it still looks like utf-8 ... I'm saying all this based on the
> assumption
cked
back out, it still looks like utf-8 ... I'm saying all this based on the
assumption that the string -> unicode difference might come from the
encoding of the PT itself?
J.F.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Chris Withers
Sent
Doyon, Jean-Francois wrote:
So I see this:
Error Type: TypeError
Error Value: 'unicode' object is not callable
Usual comments, full traceback please. This doesn't look like a normal
encoding error but a bug in code somewhere...
The only difference I can see is that the file went through su
G'day,
So I've been working on this project for some time, and all is well. Now for
the first time I migreate my product code to a brand new Zope installation on
the production systems.
Development and production systems are as identical as they can be. In this
case, they both have the same
