[doc] ctypes is too slow to convert a Python list to a C array
Open
Nobody has claimed this yet.
3.10
3.11
3.12
docs
performance
topic-ctypes
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 27926 |
|---|---|
| Nosy | @eryksun |
| Files |
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-09-01.09:31:15.237>
labels = ['ctypes', '3.8', '3.9', '3.10', 'performance']
title = 'ctypes is too slow to convert a Python list to a C array'
updated_at = <Date 2021-03-05.19:07:48.471>
user = 'https://bugs.python.org/TomCornebize'
bugs.python.org fields:
activity = <Date 2021-03-05.19:07:48.471>
actor = 'eryksun'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['ctypes']
creation = <Date 2016-09-01.09:31:15.237>
creator = 'Tom Cornebize'
dependencies = []
files = ['44320']
hgrepos = []
issue_num = 27926
keywords = []
message_count = 3.0
messages = ['274111', '274138', '274148']
nosy_count = 2.0
nosy_names = ['eryksun', 'Tom Cornebize']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'performance'
url = 'https://bugs.python.org/issue27926'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']
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 the attached ctypes_slow.py reproduction and the ctypes component, then locate the CPython path responsible for converting a Python list to a C array. Establish a focused benchmark or regression test for the reported conversion and verify that the implementation is measurably faster without changing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100