I am seeing a lot of failures with regards to widgets plus UTF-8 (unicode) encoded strings. My last failure was reported on ticket #498, but is not an isolated case.
This means that all above conditions in turbogears code would fail if an unicode encoded string was passed to it.
Since Python has two string types ('str' and 'unicode'), I believe turbogears should work with both of then transparently. This means that for the above 'grep'ed code all type conversion should be done on Python code and, IMHO, only Unicode data should reach the templates (making this destination encoding configurable and using the already existing Kid option would be really great and solve problems for people not using Unicode on their template...).
Could you please post a failing unittest so I know when I've really fixed it?
Alberto, do you mind if I send you my forms.py for this project? I don't have a failing test -- and I don't want this file to be the test, even though you can adapt it to be it later... -- right now.
Yeah, no problem... post here or send to alberto@….
It's been a while since this was solved but I can't say exactly when. It is working perfectly as of r961.
Sorry for the delay in closing this bug.