python / python/cpython

Python doesn't exit with proper resultcode on SIGINT in multiprocessing.Process

未關閉
#89,186 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

3.10 3.11 3.8 (EOL) 3.9 (EOL) interpreter-core topic-multiprocessing
主要語言
Python
星號
77.2k
分支
36k
PR 合併指標
PR 指標待擷取

描述

BPO 45023
Files
  • test.py: reproducible 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:

    assignee = None
    closed_at = None
    created_at = <Date 2021-08-26.22:56:33.544>
    labels = ['interpreter-core', '3.8', '3.9', '3.10', '3.11']
    title = "Python doesn't exit with proper resultcode on SIGINT in multiprocessing.Process"
    updated_at = <Date 2021-08-26.22:56:33.544>
    user = 'https://bugs.python.org/ambwrig'
    

    bugs.python.org fields:

    activity = <Date 2021-08-26.22:56:33.544>
    actor = 'ambwrig'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Interpreter Core']
    creation = <Date 2021-08-26.22:56:33.544>
    creator = 'ambwrig'
    dependencies = []
    files = ['50237']
    hgrepos = []
    issue_num = 45023
    keywords = []
    message_count = 1.0
    messages = ['400384']
    nosy_count = 1.0
    nosy_names = ['ambwrig']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = None
    status = 'open'
    superseder = None
    type = None
    url = 'https://bugs.python.org/issue45023'
    versions = ['Python 3.8', 'Python 3.9', 'Python 3.10', 'Python 3.11']
    

    貢獻指南

    開啟貢獻指南

    從這裡開始

    1. 先讀完整個 Issue,再讀專案的貢獻指南。
    2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
    3. Fork 儲存庫,在一個分支上完成修改。
    4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

    研究方向

    從 test.py 中的可重現範例開始並執行它,以觀察 multiprocessing.Process 接收到 SIGINT 時的退出結果。追蹤直譯器核心和 multiprocessing 的相關行為,然後驗證程序是否以預期的結果碼結束,以及該回歸是否由測試涵蓋。

    由索引模型根據 Issue 內容生成。

    評估

    技術堆疊
    python
    領域
    operating-systems
    Issue 類型
    缺陷
    難度
    4/5
    預估耗時
    3-5 天
    活躍度
    停滯
    描述清晰度
    需要釐清
    新手友好度
    30/100

    把新 issue 寄到你的電子郵件信箱

    精選適合新手參與的 GitHub issue 摘要。