ThreadPoolExecutor marks interpreter as shutdown before non daemon threads exit
@ZeroIntensity がすでに取り組んでいます。
2026年4月9日 から。
- 主要言語
- Python
- スター
- 77.2k
- フォーク
- 35.9k
- PR マージ指標
- PR 指標を取得中
説明
Bug report
Bug description:
When the main thread exits, concurrent.futures.ThreadPoolExecutor mistakenly marks the interpreter as shutdown, regardless of if there are non daemon threads still executing, this causes any work submitted to the executor to fail with RuntimeError: cannot schedule new futures after interpreter shutdown.
PoC:
import time
import threading
from concurrent.futures import ThreadPoolExecutor
def work():
print("Starting work")
time.sleep(1)
print("Work complete")
def worker_thread():
# sleep a little to give the main thread time to exit
time.sleep(1)
executor = ThreadPoolExecutor()
future = executor.submit(work)
def main():
thread = threading.Thread(target=worker_thread)
thread.start()
# main thread exits now
if __name__ == "__main__":
main()
Result
Exception in thread Thread-1 (worker_thread):
Traceback (most recent call last):
File "/usr/lib/python3.14/threading.py", line 1081, in _bootstrap_inner
self._context.run(self.run)
~~~~~~~~~~~~~~~~~^^^^^^^^^^
File "/usr/lib/python3.14/threading.py", line 1023, in run
self._target(*self._args, **self._kwargs)
~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/*****/*****/implementation/./bug.py", line 18, in worker_thread
future = executor.submit(work)
File "/usr/lib/python3.14/concurrent/futures/thread.py", line 207, in submit
raise RuntimeError('cannot schedule new futures after '
'interpreter shutdown')
RuntimeError: cannot schedule new futures after interpreter shutdown
Interpreter is marked as shutdown here: https://github.com/python/cpython/blob/f46a17b19ff535591b75f5f3df5b48f7b4f939b4/Lib/concurrent/futures/thread.py#L23-L37
Expected Result:
All non daemon threads should be able to use ThreadPoolExecutor until they exit.
example was tested on 3.14.0
cc @ZeroIntensity
CPython versions tested on:
3.14
Operating systems tested on:
Linux
コントリビューションガイド
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
評価
この issue はまだ評価されていません。