On Wed, Apr 8, 2009 at 8:19 PM, Max Ischenko <[email protected]> wrote: > > > On Wed, Apr 8, 2009 at 11:18, Max Ischenko <[email protected]> wrote: >> >> The only thing I actually need is to preserve old Mako behaviour where >> non-string values, such as ints or objects were automagically converted to >> string/unicode. >> >> How do I do this? > > Mako documentation says: > > unicode : produces a Python unicode string (this function is applied by > default). > > Obviously, this is not the case anymore. At least in my Pylons 0.9.7 code.
This again, may be way off base, but I have had problem where I talked to MySQL using latin1, but Python's version of latin1, not the full extended "windows" latin 1, then hex got into my data when it was converted, when I got to serialize it, things barf. Also, unprintable characters barf when you attempt to convert them as unicode. I might double check the data you are trying to render. Just a wild guess though. > > > > -- Cheers, Noah --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
