<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Concurrency on Aries441's Tech Blog</title><link>https://aries441.tech/tags/concurrency/</link><description>Recent content in Concurrency on Aries441's Tech Blog</description><generator>Hugo</generator><language>zh-cn</language><lastBuildDate>Mon, 29 Jun 2026 00:00:00 +0800</lastBuildDate><atom:link href="https://aries441.tech/tags/concurrency/index.xml" rel="self" type="application/rss+xml"/><item><title>Python ThreadPoolExecutor 的隐藏陷阱：主线程退出后，为什么 `submit()` 会报 `interpreter shutdown`？</title><link>https://aries441.tech/posts/tech-notes/python-threadpoolexecutor-interpreter-shutdown/</link><pubDate>Mon, 29 Jun 2026 00:00:00 +0800</pubDate><guid>https://aries441.tech/posts/tech-notes/python-threadpoolexecutor-interpreter-shutdown/</guid><description>本文复盘一个发生在 CPython 3.9+ 中的隐藏并发陷阱：当主线程先退出、非 daemon 线程继续撑住进程，而 daemon 线程随后调用 ThreadPoolExecutor.submit() 时，会触发 `cannot schedule new futures after interpreter shutdown`。文章结合源码、版本演变与官方 issue，解释其根因、触发条件与可行修复方案。</description></item></channel></rss>