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 摘要。