Message287711
| Author |
dsoprea |
| Recipients |
Vladimir Feinberg, Winterflower, davin, dsoprea, sbt |
| Date |
2017年02月13日.17:00:12 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAOr1xOFBdS5h9MuEABiYjV4iGWe2CkWL6p87tV83W4czSF_3Yw@mail.gmail.com> |
| In-reply-to |
<1487004640.22.0.448907271959.issue19675@psf.upfronthosting.co.za> |
| Content |
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 <report@bugs.python.org>
wrote:
>
> Changes by Davin Potts <python@discontinuity.net>:
>
>
> ----------
> versions: +Python 2.7, Python 3.7
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue19675>
> _______________________________________
> |
|