On Wed, May 8, 2013 at 2:00 PM, Carl Meyer <[email protected]> wrote: > Jacob has suggested that back-compat breaks in test-running are not as > serious as in production code, and that we should just switch to the new > test runner by default in Django 1.6.
I still think this. I don't see the need to maintain compatibility in testing, especially when compatibility is just a TEST_RUNNER change away. Jacob -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
