This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Claudiu.Popa
Recipients Claudiu.Popa, bquinlan
Date 2014-04-27.11:39:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1398598769.27.0.217084820664.issue21362@psf.upfronthosting.co.za>
In-reply-to
Content
Due to some bad math on my side, I passed max_workers=0 to concurrent.futures.ThreadPoolExecutor. This didn't fail properly, but hanged. The same behaviour occurs in ProcessPoolExecutor, but this time it fails internally with something like this:

Exception in thread Thread-1:
Traceback (most recent call last):
  File "C:\Python34\lib\threading.py", line 921, in _bootstrap_inner
    self.run()
  File "C:\Python34\lib\threading.py", line 869, in run
    self._target(*self._args, **self._kwargs)
  File "C:\Python34\lib\concurrent\futures\process.py", line 225, in _queue_management_worker
    assert sentinels
AssertionError

The attached patch checks that *max_workers* is <= 0 and raises ValueError if so.
History
Date User Action Args
2014-04-27 11:39:29Claudiu.Popasetrecipients: + Claudiu.Popa, bquinlan
2014-04-27 11:39:29Claudiu.Popasetmessageid: <1398598769.27.0.217084820664.issue21362@psf.upfronthosting.co.za>
2014-04-27 11:39:29Claudiu.Popalinkissue21362 messages
2014-04-27 11:39:28Claudiu.Popacreate