ok i just made a fix to this regarding filtering.
the way ${} works, whatever you put in there gets run through the
unicode() function. in the case of filtering, i was erroneously
sending the object to the filter first before the unicode()
function...in rev 172 i have fixed it so that it runs the ${}
expression through unicode() first before filtering.
when you upgrade to 172, make sure to delete any generated modules so
they recompile. while Mako has a "magic number" feature that can
cause it to regenerate templates upon upgrade, i dont feel like
bumping that up just yet.
On Jan 2, 2007, at 8:11 PM, Waldemar Osuch wrote:
Ben Bangert wrote:
Whether a filter function should handle arbitrary objects that have
no string representation is a different matter, how do other template
languages deal with that?
I am not an expert but I'm thinking that every object will have some
kind of string representation eventually. Either comming from __str__
or __repr__
Maybe filtering should be delayed until then?
Django templates also have filtering. I will poke around to see how
they handle it.
Waldemar
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
