Bah, I feel guilty.  I ran into this several months ago and reported it
here, got some feedback that I should open an issue on it but never
followed up.  So now I have:

http://code.djangoproject.com/ticket/3235

The suggestions you make for django user's code to avoid the
performance hit are valid, but I don't think django itself ought to
include a potentially big performance hit for looking up a non-existant
variable, so hopefully this will be addressed in the base code as well.

Cheers,
Karen


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

Reply via email to