`logging.shutdown()` should clear `logging._handlerList` if that's what it's called with
還沒有人認領這個 Issue。
- #129681 來自 @cjw296 —— 已關閉,未合併
- 主要語言
- Python
- 星號
- 77.2k
- 分支
- 35.9k
- PR 合併指標
- PR 指標待擷取
描述
Bug report
Bug description:
In the wild, I've encountered situations where logging.shutdown gets called more than once in a process.
The current implementation is called with logging._handlerList by default, meaning that handlers can have their flush() and close() methods called more than once, which can cause bad things to happen if those handlers are not amenable to being closed more than once.
If logging.shutdown() is processing logging._handlerList, it should clear that list once it finished to prevent handlers having their flush() and close() methods called more than once.
CPython versions tested on:
3.12, CPython main branch
Operating systems tested on:
Linux, macOS
Linked PRs
- gh-129681
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
從 logging.shutdown() 進入點開始,檢查它如何處理 logging._handlerList,包括報告中描述的對 flush() 和 close() 的重複呼叫。確認 shutdown 在處理預設處理常式清單後會清空該清單,並驗證重複呼叫 shutdown 不會再次處理相同的處理常式。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- python
- 領域
- backend
- Issue 類型
- 缺陷
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 活躍度
- 停滯
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100