thread_PyThread_start_new_thread fails with a generic error

未关闭
#60,207 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
15/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
python

调研方向

Start with the migrated BPO issue 16003 and pull request #22068, then inspect the existing discussion about thread_PyThread_start_new_thread. The issue does not name source files, tests, or the intended replacement for the generic error; completion would require determining that scope and confirming the behavior with relevant tests.

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

描述

type-feature
BPO 16003
Nosy @pitrou, @kristjanvalur, @ZackerySpytz
PRs
  • python/cpython#22068
  • 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 2012-09-23.08:34:05.959>
    labels = ['type-feature']
    title = 'thread_PyThread_start_new_thread fails with a generic error'
    updated_at = <Date 2020-09-02.16:54:01.695>
    user = 'https://github.com/kristjanvalur'
    

    bugs.python.org fields:

    activity = <Date 2020-09-02.16:54:01.695>
    actor = 'ZackerySpytz'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = []
    creation = <Date 2012-09-23.08:34:05.959>
    creator = 'kristjan.jonsson'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 16003
    keywords = ['patch']
    message_count = 2.0
    messages = ['171017', '171045']
    nosy_count = 3.0
    nosy_names = ['pitrou', 'kristjan.jonsson', 'ZackerySpytz']
    pr_nums = ['22068']
    priority = 'normal'
    resolution = None
    stage = 'patch review'
    status = 'open'
    superseder = None
    type = 'enhancement'
    url = 'https://bugs.python.org/issue16003'
    versions = ['Python 3.4']
    

    主要语言
    Python
    星标
    77.2k
    派生
    36k
    平均合并
    1 天 9 小时
    30 天内合并 PR
    558

    贡献指南

    打开贡献指南

    从这里开始

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

    python/cpython 的其他 Issue

    查看 python/cpython 的全部 Issue

    相似的 Issue

    更多 Python Issue

    把新 issue 发到你的邮箱

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