That could also work, another problem is that many times when I am debugging using tests I will use something like pbd. In this case we will always need a way to fall back to the single thread mode.
On Jan 15, 2010 2:38 AM, "Russell Keith-Magee" <freakboy3...@gmail.com> wrote: On Fri, Jan 15, 2010 at 9:59 AM, Vitaly Babiy <vbabi...@gmail.com> wrote: > I have also been thinkin... The other way to skin this particular cat is to have multiple test databases, one for each thread. This approach would require a lot more modifications to the existing test framework (to set up and allocate individual tests/test cases to each database), but it would guarantee that threads didn't end up with contention or corruption over a single database. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com<django-developers%2bunsubscr...@googlegroups.com> . For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.--
You received this message because you are subscribed to the Google Groups "Django developers" group.
To post to this group, send email to django-develop...@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.
