will that introduce performance impact since it should have hundreds T () call for each page? i understand it's better to keep the api compatible. or maybe it's good time to change the api when no one notice this problem yet?
-vince On Dec 16, 4:21 pm, mdipierro <[email protected]> wrote: > correction... I think I found a better solution, inspired by your > patch, that does not require introducing a new function and make the > example in the book work as it should. In trunk now. > > Massimo > > On Dec 16, 1:31 am, mdipierro <[email protected]> wrote: > > > This helped me understand the issue. I like it. Accepted and uploading > > to trunk now. > > Thank you Vince. > > > Massimo > > > On Dec 16, 12:55 am, vince <[email protected]> wrote: > > > > i propose this patch to make it cleaner to set current languages. > > > > -vince > > > > gluon/languages.py > > > > 57a58,61 > > > > > self.http_accept_language = request.env.http_accept_language > > > > def set_current_languages(self,languages): > > > > self.current_languages=languages > > > > self.force(languages=self.http_accept_language) > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
