Hi, Thomas Wittek filed ticket 1587 (http://trac.turbogears.org/ticket/1587).
IMHO, there should be a possibility to disable the variabledecode on a by-function basis. Obviously, this is not possible with the current implementation of NestedVariablesFilter as a CherryPy before_main filter. The latter causes problems with unit tests too if you use testutils.call. Therefore I already thought about moving the NestedVariablesFilter into the expose function (did not investigated that one thoroughly though), making the variable decoding a keyword parameter for expose (defaults to True in order to preserve the current behavior). When the current filter is moved into a decorator, the problem described by Thomas will be solved, too. Currently, I don't see any negative effects of doing this. Is the NestedVariablesFilter already implemented for TG 2? Does Pylons integrate this feature? If not I think moving the functionality into a decorator would ease the transition from CherryPy to Pylons. Comments welcome. fs
smime.p7s
Description: S/MIME Cryptographic Signature
