I can reproduce it, with LANG=fr_FR.UTF-8. (it errors out on "patate sucrée") It seems to be a bug that a lot of applications using sqlalchemy stumble upon (just look for the error message in google). The problem lies somewhere between pysqlite (that prohibited the use of byte strings since 2.5.0, only allowing unicode _objects_, not just unicode byte strings) and sqlalchemy (whose upstream patch doesn't seem to solve anything). See http://code.djangoproject.com/ticket/7921 for a good explanation.
Sorry I don't have time to investigate further, but I see no quick workaround (well, prependeing all strings in defaults*.py with 'u' so that they become unicode objects, as the file is already completely utf8-encoded, may be a hackish workaround). Upstream should clearly do something on this. BTW, this problem isn't reproduced if you've already built the initial database once. For those of you who didn't see this, rm your ~/.gourmet. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
