On 8/29/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > Personally, I find myself leaning towards option 3 - outside of testing, I > can't see any use case for a template-rendering signal, and I don't like > special cases. Instrumentation of the rendering system as part of the test > framework setup seems an appropriate solution. >
My personal preference is for option 3. While testing is incredibly important, a site with decent traffic will spend 99% of its execution time, over its lifetime, responding to actual requests, as opposed to running tests. Some might call it premature optimization, but I'd prefer not to see something go in that will essentially result in wasted cycles 99% of the time. And remember that even for option 2, there's not just the cost of a boolean comparison. There's also the cost of a namespace lookup to get 'TESTING' from 'settings', unless you want to do a 'from settings import TESTING'. Jay P. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers -~----------~----~----~----~------~----~------~--~---
