Thanks so much for the replies Chris and asm.
I tried the suggested fix with the ".decode.('cp1252')" and yes that
works great for avoiding the crash - thank you again, I never would
have known to try that!
Because you described that fix as "quick/dirty", I'm also wondering if
there's any broader solution that I should consider for the longer
term to help lessen the chance of such invalid data griding my app to
a halt? Any thoughts?
On Jul 5, 10:02 am, Christoph Zwerschke <[EMAIL PROTECTED]> wrote:
> > to increase the confusion, Kid outputs a wrong error message, probably
> > becasuse of this Python bug: ...
>
> This turned out to be a bug in Kid, not Python. UnicodeDecodeErrors are
> erroneously "translated" to these TypeErrors by Kid. Will be solved in
> the next Kid version.
>
> -- Chris
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" 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/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---
