On Tue, May 17, 2011 at 12:59 PM, Jonas H. <[email protected]> wrote: > On 05/17/2011 04:48 PM, Jeremy Dunck wrote: >>> >>> 1) Use file modification timestamps for all model and test related files. >>> Advantages: simple, works. >>> Disadvantages: Triggers cache invalidation for changes not related to >>> models >>> or tests >> >> I think this is a pretty big win, even though it's not theoretically >> optimal. > > Only for "does-it-still-work" sort of tests. Not for test-driven > development, because your models and tests change all the time. >
Well, we're debating various ways to improve, and I'm saying, let's do the simplest thing that will work to raise the chance that it'll actually get done. :-) I declare myself bike-shedding. Given the 3 options, I'm: +1 on #1 +0 on #2 -0 on #3 -- 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?hl=en.
