it works, I don't know why but...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
gt;
> everything is utf-8 compliant (db = sqlite3) so I don't understand,
> the error happenned in *force_unicode*.
>
> any tips
Dealt with a LOT of unicode errors after the upgrade - some happened
due to workarounds to django bugs that turned to bugs in my code, and
the rest wa
here are my models http://dpaste.com/66067/
I use smart_unicode even if it's already UTF-8 and no more error but
nothing appears in the admin detailed view of posts
On 19 juil, 14:49, Amirouche <[EMAIL PROTECTED]> wrote:
> I'm using the trunck version
>
> Environment:
>
> Request Method: GET
> R
I'm using the trunck version
Environment:
Request Method: GET
Request URL: http://127.0.0.1:8000/admin/blogfeeds/post/15/
Django Version: 0.97-newforms-admin-SVN-7977
Python Version: 2.5.2
Installed Applications:
['django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
Hi,
Could you post the whole traceback? Also, precise what version of
Django you're using. Without that info it's a bit hard to help you.
Cheers,
Julien
On Jul 19, 10:01 pm, Amirouche <[EMAIL PROTECTED]> wrote:
> I got an encoding error while rendering in the admin some text I
> parsed from a
I got an encoding error while rendering in the admin some text I
parsed from a feed with feedparser
Caught an exception while rendering: 'ascii' codec can't encode
character u'\u2605'.
everything is utf-8 compliant (db = sqlite3) so I don't understand,
the error happenned in *force_unicode*.
a
Ouch, there was a % in the generated SQL. Guess I should have debugged
a little more before posting here. :)
On Apr 5, 1:44 pm, shabda <[EMAIL PROTECTED]> wrote:
> I am using MYSql with latin-1 encoding.
>
> I get some weird intermittent errors when using custom sql. I have a
> large programatica
I am using MYSql with latin-1 encoding.
I get some weird intermittent errors when using custom sql. I have a
large programatically generated sql, and when I try to run this as
cursor.execute(sql), it works sometime but fails other times. The only
big difference I can see between the sqls is that
8 matches
Mail list logo
