On Mon, 2007-12-03 at 00:03 -0800, SmileyChris wrote: > On Dec 3, 6:02 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> > wrote: > > What method? > > lazy()
Of course it works. We're using it throughout Django for lazy translations. Keep in mind though that most of the stuff in django.utils is for Django's internal usage and lazy() is certainly fit for its purpose. I guess what your original post was trying to say is that it doesn't work for all return types because sometimes methods on the underlying type have to be replaced. However, we don't need that (lazy() is predominantly used for string types) and so I've avoided adding the extra code to work all that out. lazy() is complex enough without adding things we don't need. If there's a legitimate case where Django core needs this extra functionality, I'd probably first try to work out how to avoid it and only then add it. If you're trying to use it as a general external things... well, as the joke goes "Doctor it hurts when I do this...". Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
