python / python/cpython

Inconsistent Behavior Of futures.ProcessPoolExecutor

未关闭
#79,058 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

3.7 (EOL) interpreter-core topic-multiprocessing
主要语言
Python
星标
77.2k
派生
36k
PR 合并指标
PR 指标待抓取

描述

BPO 34877
Nosy @tirkarthi, @TensorTom
Files
  • brokenPool.py: Example code
  • 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 2018-10-02.23:16:54.387>
    labels = ['interpreter-core', '3.7']
    title = 'Inconsistent Behavior Of futures.ProcessPoolExecutor'
    updated_at = <Date 2018-10-03.00:15:28.564>
    user = 'https://github.com/TensorTom'
    

    bugs.python.org fields:

    activity = <Date 2018-10-03.00:15:28.564>
    actor = 'xtreak'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Interpreter Core']
    creation = <Date 2018-10-02.23:16:54.387>
    creator = 'TensorTom'
    dependencies = []
    files = ['47843']
    hgrepos = []
    issue_num = 34877
    keywords = []
    message_count = 1.0
    messages = ['326922']
    nosy_count = 2.0
    nosy_names = ['xtreak', 'TensorTom']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = None
    status = 'open'
    superseder = None
    type = None
    url = 'https://bugs.python.org/issue34877'
    versions = ['Python 3.7']
    

    贡献指南

    打开贡献指南

    从这里开始

    1. 先读完整个 Issue,再读项目的贡献指南。
    2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
    3. Fork 仓库,在一个分支上完成修改。
    4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

    调研方向

    首先运行提供的 brokenPool.py 示例,并阅读它所展示的 ProcessPoolExecutor 行为。根据复现结果和项目上下文确定预期行为,然后在处理这一不一致之前添加一个针对性的回归测试。

    由索引模型根据 Issue 内容生成。

    评估

    技术栈
    python
    领域
    backend
    Issue 类型
    缺陷
    难度
    4/5
    预计耗时
    3-5 天
    活跃度
    停滞
    描述清晰度
    需要澄清
    新手友好度
    25/100

    把新 issue 发到你的邮箱

    精选适合新手参与的 GitHub issue 摘要。