Determining the failure of C API call is ambiguous

未關閉
#70,963 2 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

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

研究方向

Start by reviewing the linked check_error_occurred.patch and the original BPO issue 26776. Investigate how the affected C API call reports failure and determine what behavior the patch proposes. Done means the failure result is no longer ambiguous, with the relevant interpreter-core behavior covered by the project’s existing checks.

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

描述

interpreter-core topic-C-API
BPO 26776
Nosy @vstinner, @serhiy-storchaka
Files
  • check_error_occurred.patch
  • 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 2016-04-16.08:02:38.488>
    labels = ['interpreter-core']
    title = 'Determining the failure of C API call is ambiguous'
    updated_at = <Date 2016-04-16.09:27:24.259>
    user = 'https://github.com/serhiy-storchaka'
    

    bugs.python.org fields:

    activity = <Date 2016-04-16.09:27:24.259>
    actor = 'vstinner'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Interpreter Core']
    creation = <Date 2016-04-16.08:02:38.488>
    creator = 'serhiy.storchaka'
    dependencies = []
    files = ['42478']
    hgrepos = []
    issue_num = 26776
    keywords = ['patch']
    message_count = 2.0
    messages = ['263540', '263544']
    nosy_count = 2.0
    nosy_names = ['vstinner', 'serhiy.storchaka']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = None
    status = 'open'
    superseder = None
    type = None
    url = 'https://bugs.python.org/issue26776'
    versions = []
    

    主要語言
    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 摘要。