4 ms·
RE: multiprocessing - Did you file any bugs on it? I agree that there is slightly too much magic, and I'm looking at reducing it - but bug reports and/or patche
by jnoller 18y ago
RE: multiprocessing - Did you file any bugs on it? I agree that there is slightly too much magic, and I'm looking at reducing it - but bug reports and/or patches help me. Right now, my focus is on fixing the docs for 2.6.1 and 3.0 final and further expanding the tests.
- tdavis 18y agoI 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...
- jnoller 18y agoFair enough :) I'm going to make it a task to document, clean up and possibly remove some of the magic.