[issue26523] multiprocessing ThreadPool is untested

2016-03-15 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- resolution: -> fixed stage: commit review -> resolved status: open -> closed ___ Python tracker ___ __

[issue26523] multiprocessing ThreadPool is untested

2016-03-15 Thread Roundup Robot
Roundup Robot added the comment: New changeset 4cabf12b7fc6 by Antoine Pitrou in branch '3.5': Issue #26523: The multiprocessing thread pool (multiprocessing.dummy.Pool) was untested. https://hg.python.org/cpython/rev/4cabf12b7fc6 New changeset 131f92510164 by Antoine Pitrou in branch 'default'

[issue26523] multiprocessing ThreadPool is untested

2016-03-15 Thread Antoine Pitrou
Antoine Pitrou added the comment: > Is it worth to change multiprocessing.Pool in _TestPoolWorkerErrors > and _TestPoolWorkerLifetime? Currently they work only for processes, > but may be they can be generalized. Perhaps as another issue? It may be more involved than this one. --

[issue26523] multiprocessing ThreadPool is untested

2016-03-14 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- assignee: -> pitrou stage: patch review -> commit review ___ Python tracker ___ ___ Python-bugs-list

[issue26523] multiprocessing ThreadPool is untested

2016-03-09 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: LGTM. Is it worth to change multiprocessing.Pool in _TestPoolWorkerErrors and _TestPoolWorkerLifetime? Currently they work only for processes, but may be they can be generalized. -- nosy: +serhiy.storchaka ___ Py

[issue26523] multiprocessing ThreadPool is untested

2016-03-09 Thread Ned Deily
Changes by Ned Deily : -- nosy: +davin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/

[issue26523] multiprocessing ThreadPool is untested

2016-03-09 Thread Antoine Pitrou
Antoine Pitrou added the comment: Turns out a couple of tests were calling multiprocessing.Pool directly, updating patch. -- Added file: http://bugs.python.org/file42108/test_threadpool2.patch ___ Python tracker _

[issue26523] multiprocessing ThreadPool is untested

2016-03-09 Thread Antoine Pitrou
New submission from Antoine Pitrou: There is a mistake in _test_multiprocessing.py which means that ThreadPool is untested, the regular Pool is tested instead by the ThreadsMixin. Patch attached. -- components: Library (Lib), Tests files: test_threadpool.patch keywords: patch messages