unknown encoding cp0 when encountering a print command

[benedict.verheyen@…]

This error occurs after r5600 (unicode merge).
My view uses a class that also is used as a standalone class in other software.
The class generates a password amongst other things and the prints that to the console.

def report(self):

print "Paswoord: %s " % self.paswoord

After revision 5600, these print command result in the afor mentioned error
I tried adding an enconding stanza to the top of the source file but that didn't work.

[benedict.verheyen@…]

html file containing the traces of the error

[benedict.verheyen@…]

code of the class containing the print commands

[benedict.verheyen@…]

I tried to add the error trace but Akismet says it's spam.
If you want the trace, check the gmane django newsgroup, i've made a post
with the title "unknown encoding cp0" also that contains the trace or mail me
for the trace

[Michael Radziej]

The ticket system is not for user support. Please consult the unicode documentation and ask at the django-user mailing list for help. The unicode change contains backwards-incompatible changes, and you need to adapt your code.

[benedict.verheyen@…]

I know this is not meant for support and I asked already on the user mailing list (no response).
That's why i thought it was a bug.
Since you seem to be knowledgable on the subject of this error, it would be handy if you could
point to the exact documentation that deals on this subject instead of just saying
"Please consult the unicode documentation".

[Michael Radziej]

Well, please attach at least the model, the full backtrace, your settings.ini. The unicode docs are at
​http://www.djangoproject.com/documentation/unicode/
(or follow the second like that google gives for 'django unicode')

BTW, the list of backwards incompatible changes is at
​http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges.
you should read them before you update to a later svn revision.

Both are linked from the main Django documentation page (guess what google 'django documentation' brings up?)

I don't know about your email to the list, but if you've put in as 'much' detail like in this ticket, no wonder that you haven't got any response.

[Michael Radziej]

Ah, I forgot this link, which might be most useful to you (and it's actually not so easy to spot):

​http://code.djangoproject.com/wiki/UnicodeBranch#PortingApplicationsTheQuickChecklist

[benedict.verheyen@…]

Thanks, that link is useful.
As for your last comment "but if you've put in as 'much' detail like in this ticket, no wonder that you haven't got any response"
I did provide the backtrace and code in the newsgroup post and i tried to do the same here.

However, the trace was rejected by your system (Akismet what ever that is). See the change history:

"I tried to add the error trace but Akismet says it's spam. If you want the trace, check the gmane django newsgroup, i've made a post with the title "unknown encoding cp0" also that contains the trace or mail me for the trace"

So it's not like i didn't try eh.