[issue37208] Weird exception behaviour in ProcessPoolExecutor

Change by Brian Quinlan : -- stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue37208] Weird exception behaviour in ProcessPoolExecutor

Change by F. Raab : -- nosy: +raabf ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/m

[issue37208] Weird exception behaviour in ProcessPoolExecutor

Change by Brian Quinlan : -- resolution: -> duplicate superseder: -> picke cannot dump Exception subclasses with different super() args ___ Python tracker ___ __

[issue37208] Weird exception behaviour in ProcessPoolExecutor

Brian Quinlan added the comment: That's a super interesting bug! It looks like this issue is that your exception can't be round-tripped using pickle i.e. >>> class PoolBreaker(Exception): ... def __init__(self, num): ... super().__init__() ... self.num = num ... >>> impor

[issue37208] Weird exception behaviour in ProcessPoolExecutor

Change by Karthikeyan Singaravelan : -- nosy: +bquinlan, pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue37208] Weird exception behaviour in ProcessPoolExecutor

New submission from Iceflower : 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