On 4/25/06, Vasily Sulatskov <[EMAIL PROTECTED]> wrote:
I used to use setdefaultencoding but now I consider it a dangerous one. Maybe the problem was that I was using it from sitecustomize.py (how else can you use it :) and it affected all programs. Later when I learned better (to place it inside my app dir), I already stopped using sitecustomize.
I'm also interested how can locale module help.
Tvrtko
Hello Jonathan,
>> 2. engine.client_encoding - encoding for client side strings, i.e.
>> string that user feeds to sqlalchemy or gets from it. Defaults to
>> 'ascii', or some other encoding common to most of
>> sqlalchemy users
> Unnecessary to have a separate SA setting. That's what the locale module is
> for; use that instead.
Can you be more specific, please?
I can't find anything in locale module that will help in this case.
There is a sys.setdefaultencoding() function, but I actually never
managed to get it work...
I used to use setdefaultencoding but now I consider it a dangerous one. Maybe the problem was that I was using it from sitecustomize.py (how else can you use it :) and it affected all programs. Later when I learned better (to place it inside my app dir), I already stopped using sitecustomize.
I'm also interested how can locale module help.
Tvrtko
