> If I personally were given the choice between cache.clear() and nothing at > all, i'd take cache.clear() and be careful with it. But I'm not sure if the > rest of the community is willing to accept such a solution. Hence the > CLEAR_BETWEEN_TESTS flag as a compromise.
But the flag doesn't solve the memcached issue, right? IMHO, it only adds to the false impression that you can have any control on what gets flushed by memcached. I also agree with Aymeric that not clearing cache state is a bug. Having a flag to fix/restore buggy behaviour seems weird. -- Łukasz Rekucki -- 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 django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
