Test framework doesn't install _(), maybe?

[dave AT avaragado.org]

The call to render_to_response includes the i18n magic _ function, but it hasn't been imported. Result: grief, in conjunction with the new test client at least (it gives me a 500 response).

To fix: import _ from the usual place. I trust a patch submission for this change is not required :-)

[Adrian Holovaty]

The _ function isn't meant to be imported, as django.utils.translation.trans_real.install automatically puts it in the global namespace. I suspect this is a problem with the testing framework, then...

[mir@…]

I had exactly this problem with my own test stuff, and the problem turned out to be a little bit nasty. I use py.test together with doctests. During doctests, _ will be overwritten with each evaluated value, as happens during interactive use.

I solved it by doing

__builtins__['_'] = gettext

after each doctest. You can't use the '_' of i18n in doctests, but this never a problem for me.

Perhaps this can be done in the new django test framework, too.

[Michael Radziej <mir@…>]

duplicate of #2920