python / python/cpython

PyObject_Call not behaving as documented

未關閉
#86,795 4 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

3.9 (EOL) topic-C-API type-bug
主要語言
Python
星號
77.2k
分支
36k
PR 合併指標
PR 指標待擷取

描述

BPO 42629
Nosy @MojoVampire, @maxbachmann

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 2020-12-13.00:21:25.725>
labels = ['expert-C-API', 'type-bug', '3.9']
title = 'PyObject_Call not behaving as documented'
updated_at = <Date 2020-12-16.14:42:35.640>
user = 'https://github.com/maxbachmann'

bugs.python.org fields:

activity = <Date 2020-12-16.14:42:35.640>
actor = 'josh.r'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['C API']
creation = <Date 2020-12-13.00:21:25.725>
creator = 'maxbachmann'
dependencies = []
files = []
hgrepos = []
issue_num = 42629
keywords = []
message_count = 2.0
messages = ['382927', '383173']
nosy_count = 2.0
nosy_names = ['josh.r', 'maxbachmann']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue42629'
versions = ['Python 3.9']

貢獻指南

開啟貢獻指南

從這裡開始

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

研究方向

從 PyObject_Call C API 進入點開始,檢視 BPO 42629 所參照的文件。該 issue 未指出原始檔、測試、預期行為或具體重現方式,因此首先確定文件描述與實際觀察到的行為之間的差異;完成的標準是行為與文件和涵蓋該問題的回歸測試一致。

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

評估

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

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

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