Enhance filters.Decode unicode handling

Issue #47 resolved
created an issue

Right now, even when using filters.decode.utf8, it's possible to get str object after filter - when using some object which is not instance of basestring.

For example when using Mako with Django oldforms, Mako will crash on something like

${ form['country'] }

Because form['country'] is a !FormFieldWrapper instance, and it doesn't get decoded by filter.decode.utf8.

So here's the small patch that will decode using given encoding even not basestring objects after converting object to string using str().

Comments (1)

  1. Log in to comment