Malcolm Tredinnick wrote: > On Mon, 2007-05-28 at 11:27 +0200, Michal wrote: >> Malcolm Tredinnick wrote: >>> On Mon, 2007-05-28 at 02:09 -0700, itsnotvalid wrote: >>>> Michal, your error looks nearly identical to the one I encounter with >>>> admin interface. Except the byte offending is not the same. >>>> >>>> I guess there is something between the model class and database >>>> adapters which adds those strange bytes. >>> No, there's nothing like that. These are just standard ASCII decoding >>> errors that Python reports. A byte starting with 'C' in the high nibble >>> (e.g. Michal's 0xc3) is the start of a two-byte UTF-8 sequence, >>> something like your 0xe4 is the first byte of three byte UTF-8 sequence >>> (or possibly some non-UTF-8 bytes altogether, in both cases). >> Hmm... Sorry, but I could't locate this problem (before my last update >> to revivision 5371) > > When you say "this problem", which problem do you mean? The one you > reported in your first email? Because in the email fragment you quoted > from me, there is no "problem" reported. > > I'm very happy to help fix these errors people are seeing; they are all > small things and easy to nail with a good explanation, but you have to > help me help you: what is failing? Remember that there are about four > different sub-threads going on under this topic, so giving replying to > the right email so that the right replies thread together is going to be > useful, too. > > If this is the problem you reported in your first email, the simplest > thing you can do to help is work out which model's verbose name is > causing problems. From reading your email, I suspect you have a UTF-8 > string being used as a verbose_name somewhere (which is perfectly fine) > and it uses some codepoints outside the ASCII range. I've just finished > eating dinner and am about to try and test that theory, because my gut > feeling is that will cause a traceback, just from reading the code. > > Assuming it's what I think it is, this will be fixed in about 30 > minutes.
Sorry for confusions Malcolm. My note was in relation with latest error (ie. I have problem with execution of tests due to verbose_name error). I am just after dinner too, so I will try to find what is wrong in my application... :) Once again, sorry for my obscure latest report and english. Michal --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
