Michael Radziej napisał(a): >>>> The next testing option is to try with non-lazy version. >>> that works! import gettext as _ >> And that's a real bug, I think. >> >> Anyway, for future reference, keep in mind that lazily translated >> "strings" become real strings at access time. Before that they are >> function objects. That is, you cann't, for example, pickle them - and in >> consequence put in session because session data is pickled before >> saving. Laziness isn't always good. ;) > > If I haven't mistaken anything, we're talking about the choices setting in > model fields. The models are read in during initialization. But the choices > need to be translated for each request, and for different languages. I don't > see how this could work without lazy translation, and I'd be astonished if > the solution above really worked.
True, that's why I call this behaviour "buggy". -- Jarek Zgoda Skype: jzgoda | GTalk: [EMAIL PROTECTED] | voice: +48228430101 "We read Knuth so you don't have to." (Tim Peters) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
