I didn't file a bug report because I'm not entirely sure what I would file it as; "Excessive use of magic?". What happened in my case is that when using multip

I didn't file a bug report because I'm not entirely sure what I would file it as; "Excessive use of magic?". What happened in my case is that when using multiprocessing with Django, if a database connection is opened by the main process to make a query that connection is kept open and workers end up using it instead of spawning their own. If I manually close the connection, they all make their own. This isn't sufficient, however, because global imports related to transaction support still manage to step on each other when queries are run concurrently. This turns out to be a pretty rare race condition, but it does happen. You can read more at the comment here, including my workarounds: http://ericholscher.com/blog/2008/nov/10/announcing-django-crawler-test-utils/#c211 http://ericholscher.com/blog/2008/nov/10/announcing-django-c...