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 Iceflower
Recipients Iceflower
Date 2019-06-09.11:04:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1560078240.39.0.310143322777.issue37208@roundup.psfhosted.org>
In-reply-to
Content
I don't really know where this belongs, but it is at least for me not an expected behaviour. It is weird for me at all. Please take a look if this is an intended behaviour and why it is like that.

Tested with py3.7.3, py3.8.0b1
```
A process in the process pool was terminated abruptly while the future was running or pending.
```

Tested with py 3.6.8:
```
Exception in thread Thread-1:
Traceback (most recent call last):
  File "C:\Python36\lib\threading.py", line 916, in _bootstrap_inner
    self.run()
  File "C:\Python36\lib\threading.py", line 864, in run
    self._target(*self._args, **self._kwargs)
  File "C:\Python36\lib\concurrent\futures\process.py", line 272, in _queue_management_worker
    result_item = reader.recv()
  File "C:\Python36\lib\multiprocessing\connection.py", line 251, in recv
    return _ForkingPickler.loads(buf.getbuffer())
TypeError: __init__() missing 1 required positional argument: 'num'
```

I expect that the PoolBreaker exception would work too.

Code to test:
As attachment.
History
Date User Action Args
2019-06-09 11:04:00Iceflowersetrecipients: + Iceflower
2019-06-09 11:04:00Iceflowersetmessageid: <1560078240.39.0.310143322777.issue37208@roundup.psfhosted.org>
2019-06-09 11:04:00Iceflowerlinkissue37208 messages
2019-06-09 11:04:00Iceflowercreate