> No. Prior to 1.0 we are going to remove the implicit and automatic > aliasing of gettext() to _() throughout the code anyway. It's a bit of a > Python design wart -- i.e. they *really* didn't think it through. The > problem is that if you rely on the it always being in builtins, doctests > (and interactive shell work) break. In fact, I'm pretty sure that's > somewhat the cause of the problem you're seeing. Remember that _ is used > as "the last result" in the Python interactive prompt.
ok, thanks again. But I can say the problem is not just the interactive shell. I resorted to use it becouse the code that always worked gave me that exact error. Anyhow I will just import explicitely. sandro *:-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
