PyArg_Parse* for vectorcall?
Open
Nobody has claimed this yet.
3.11
topic-argument-clinic
topic-C-API
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 44214 |
|---|---|
| Nosy | @ronaldoussoren, @jkloth, @methane, @serhiy-storchaka |
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-05-23.10:14:52.625>
labels = ['expert-C-API', 'type-feature', '3.11']
title = 'PyArg_Parse* for vectorcall?'
updated_at = <Date 2021-05-25.15:39:24.008>
user = 'https://github.com/ronaldoussoren'
bugs.python.org fields:
activity = <Date 2021-05-25.15:39:24.008>
actor = 'serhiy.storchaka'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['C API']
creation = <Date 2021-05-23.10:14:52.625>
creator = 'ronaldoussoren'
dependencies = []
files = []
hgrepos = []
issue_num = 44214
keywords = []
message_count = 4.0
messages = ['394194', '394195', '394363', '394372']
nosy_count = 4.0
nosy_names = ['ronaldoussoren', 'jkloth', 'methane', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue44214'
versions = ['Python 3.11']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with BPO issue 44214 and its C API context; the payload names no implementation files, tests, or entry points. Clarify the intended PyArg_Parse* and vectorcall behavior with the existing nosy participants, then define the accepted API change and its verification before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100