That looks like a file that hasn't been ported properly to the latest
code. Once upon a time, Django automatically provided the gettext()
function via the alias _(). However, that changed after we added unicode
support, for a few different reasons, so code has to explicitly import
the right translation function. That particular function provides
internationalisation support: the error string will be translated into
the currently active language.
The correct solution is to add
from django.utils.translation import ugettext as _
to the top of the file. Looks like somebody reported this ([1]),
although their patch uses gettext() instead of ugettext() -- the latter
is a better habit to get into these days.
[1] http://code.google.com/p/django-rest-interface/issues/detail?id=31
Regards,
Malcolm
The last time i tested this code was just after the 1.0 release and my
code is still running off that. I had some trouble reproducing some of
the bugs...i just make sure that the test cases run every once in a
while.
I'll try to take care of this bug this weekend.
Thanks everyone for the heads up.
--
Regards,
Alaa Salman
http://www.codedemigod.com
FSF Member #6304
"Never measure the height of a mountain until you have reached the
top. Then you will see how low it was." ---Dag Hammarskjold