On 7/6/07, Chris Shenton <[EMAIL PROTECTED]> wrote:
>
>
> I had issues in the past with (for example) umlauted-chars being
> entered into my data that then couldn't be rendere by Myghty with the
> default ascii codec; changing python's sitecustomize.py to use:
>
> sys.setdefaultencoding("utf-8")
first of all, definitely dont use sys.setdefaultencoding, that is a
hack of the most brittle kind.
but secondly, upgrade your MySQLDB (i.e., the mysql-python DBAPI). it
most certainly had a double-encoding bug some time ago, you can find
it in their bug tracker and ours (sqlalchemy's).
--~--~-
On 7/6/07, Chris Shenton <[EMAIL PROTECTED]> wrote:
>
> I had issues in the past with (for example) umlauted-chars being
> entered into my data that then couldn't be rendere by Myghty with the
> default ascii codec; changing python's sitecustomize.py to use:
>
> sys.setdefaultencoding("utf-8")
I had issues in the past with (for example) umlauted-chars being
entered into my data that then couldn't be rendere by Myghty with the
default ascii codec; changing python's sitecustomize.py to use:
sys.setdefaultencoding("utf-8")
has fixed this -- until now.
My user uploaded a CSV file us
