You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2018-12-13.01:15:47.499>created_at=<Date2018-12-12.23:08:12.351>labels= ['3.8', 'library']
title='multiprocessing.Pool.__enter__() should raise an exception if called twice'updated_at=<Date2018-12-13.01:15:47.498>user='https://github.com/vstinner'
fails with "ValueError: I/O operation on closed file", because file.__enter__() raises this exception if the file is closed.
I propose to have the same behavior on multiprocessing.Pool.__enter__() to detect when the multiprocessing API is misused.
Anyway, after the first "with pool:" block, the pool becomes unusable to schedule now tasks: apply() raise ValueError("Pool not running") in that case for example.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: