> > It would be nice to know if by using the decoding filter we can remove
> > some of the hacks we are using ATM, like to_unicode in widgets and fix
> > #430, we may want to also ping Max.

I think this is a welcome addition. It certainly doesn't solve
everything but at least out-of-the box experience is better - you don't
have to put UnicodeString validator everywhere.  And it is backward
compatible - at least, if you did use the validator before.

In fact, I was surprised when I started using TG that input parameters
are not decoded - it seemed a bit counterintuitive because data _was_
encoded on output. I didn't knew about CherryPy filter and learnt to
use UnicodeString validator.

One (minor) consideration: if you'd ever want to rollback this decision
it will break the code. So, once you added automatic coercion of input
data we'd better keep it.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears Trunk" 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-trunk
-~----------~----~----~----~------~----~------~--~---

Reply via email to