Benedict Verheyen schreef:
> Nis Jørgensen schreef:
> <snip>
>
>>>
>> What is "self" referring to? Can you give us a stack trace? And which
>> version of Django are you running (it is especially important to know if
>> it is before or after the unicode branch got merged).
I could test it by reverting my local svn version to an older version,
before the unicode branch got merged.
What revision would that be?
Hhhmn, i check the commit logs and revision 5600 should be the version
just before the unicode branch got merged.
I checked out version 5600 (i did a svn co -r5600 in another directory.
Is there a better way to do this? revert?) and tried it and i don't get
the encoding error !
So it looks like it probably has to do with the unicode merge.
Maybe this part of the link that i posted in my first post could help:
- if _cached_user_encoding is None:
+ # Windows returns 'cp0' to indicate there is no code page. So we'll
just
+ # treat that as ASCII, and not support printing unicode characters
to the
+ # console.
+ if _cached_user_encoding in (None, 'cp0'):
_cached_user_encoding = 'ascii'
return _cached_user_encoding
Regards,
Benedict
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
