There is a proposal by Alvaro to remove lazyT from languages.py
This means that T("translate me") will return a translated string
instead of a lazyT object that is instantiated when included in text
or when forced via str(T(....)).

The change would speed up translation a bit and make the syntax
cleaner but it would prevent users from setting the current language
after T is used the first time. This would be a soft break of backward
compatibility since I do not believe anybody is relying on lazyT.

Can you help us point out pros and cons?

Massimo
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to