7 messages in com.googlegroups.pylons-discussRe: Upgrading to 0.9.5 - unicode issue
FromSent OnAttachments
Robert Leftwich28 Apr 2007 00:42 
Max Ischenko28 Apr 2007 04:06 
Robert Leftwich28 Apr 2007 04:21 
Max Ischenko28 Apr 2007 04:26 
Ben Bangert28 Apr 2007 10:08 
Shannon -jj Behrens01 May 2007 16:55 
Robert Leftwich01 May 2007 17:40 
Subject:Re: Upgrading to 0.9.5 - unicode issue
From:Max Ischenko (isch@public.gmane.org)
Date:04/28/2007 04:06:03 AM
List:com.googlegroups.pylons-discuss

Hello,

I am afraid I can't give a helpful answer but I'll tune in anyway. ;)

On 4/28/07, Robert Leftwich <pylo@public.gmane.org>
wrote:

I'm just attempting an upgrade to 0.9.5 and a lot of pages starting failing with "unicode' object has no attribute 'is_file_component'" errors. This looks to be happening because the controller params are now all being sent as unicode objects and in most cases I'm using at least one param to dynamically generate the Myghty template name I want to render and these names are now unicode objects instead of strings, which Myghty does not seem to handle.

Hmm. The str class doesn't have 'is_file_component' either, does it?

My app's running on 0.9.5 just fine but it doesn't use Myghty.

I note in the internationalisation document it mentions using a

request_settings in the config, which I *don't* have, as the way I read it, you only need to use this dict to turn the coercion on, implying it is off by default.

Is there a way to stop this automatic coercion of these params to unicode or do I need to tackle this problem in some other way?

If you want to turn it off I believe you need to dig into Paste, not Pylons because it happens there IIRC.

Max.