Message342260
@asvetlov The idea of the new flag is to disable any subsequent waiting for futures after ThreadPoolExecutor.shutdown(wait=False) returns.
Currently the additional waiting is implemented using "atexit", so I assumed it referred to process exit. (The documentation at https://docs.python.org/3/library/atexit.html doesn't seem to specify precisely when the callbacks are executed.) But looking at the implementation of atexit, it seems that the atexit callbacks are actually called from Py_FinalizeEx.
I think wait_at_exit is descriptive because in most cases the process exit and interpreter shutdown will correlate, but I can still update the docs to make it clearer what "exit" refers to. We should just avoid the word "shutdown" in the flag name to avoid confusion with executor shutdown. |
|
Date |
User |
Action |
Args |
2019-05-12 14:52:59 | hniksic | set | recipients:
+ hniksic, bquinlan, pitrou, asvetlov |
2019-05-12 14:52:59 | hniksic | set | messageid: <1557672779.25.0.171066375922.issue36780@roundup.psfhosted.org> |
2019-05-12 14:52:59 | hniksic | link | issue36780 messages |
2019-05-12 14:52:58 | hniksic | create | |
|