Dustin Oprea added the comment: Okay. Thanks for weighing-in.
I'm trying to figure out how to write the tests. The existing set of tests for multiprocessing is a near nightmare. It seems like I might have to use one of the existing "source code" definitions to test for the no-cleanup (traditional) scenario but then have to define a new one to define the pool with an initializer that fails. However, then, I'll have to define three new TestCase-based classes to test for the various start-methods. Any suggestions? On Mon, Feb 13, 2017 at 11:50 AM, Davin Potts <rep...@bugs.python.org> wrote: > > Changes by Davin Potts <pyt...@discontinuity.net>: > > > ---------- > versions: +Python 2.7, Python 3.7 > > _______________________________________ > Python tracker <rep...@bugs.python.org> > <http://bugs.python.org/issue19675> > _______________________________________ > ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue19675> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
