Add 128-bit integer support to struct
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reading the struct and ctypes entry points related to integer formats; the issue names no files or tests, so first determine where existing integer support is implemented. Clarify the intended 128-bit behavior and identify the relevant test location before making changes. Done means 128-bit integer support is implemented and covered by tests.
Written by the indexing model from the issue text.
Description
| BPO | 19904 |
|---|---|
| Nosy | @tim-one, @gpshead, @mdickinson, @pitrou, @alex, @meadori, @nanjekyejoannah |
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 2013-12-06.02:04:23.032>
labels = ['ctypes', 'type-feature']
title = 'Add 128-bit integer support to struct'
updated_at = <Date 2019-05-27.19:23:17.757>
user = 'https://bugs.python.org/fil'
bugs.python.org fields:
activity = <Date 2019-05-27.19:23:17.757>
actor = 'nanjekyejoannah'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['ctypes']
creation = <Date 2013-12-06.02:04:23.032>
creator = 'fil'
dependencies = []
files = []
hgrepos = []
issue_num = 19904
keywords = []
message_count = 15.0
messages = ['205344', '205357', '205399', '205400', '205403', '205431', '205447', '205574', '205626', '205627', '205628', '205629', '205634', '205763', '205765']
nosy_count = 9.0
nosy_names = ['tim.peters', 'gregory.p.smith', 'mark.dickinson', 'pitrou', 'alex', 'meador.inge', 'francismb', 'fil', 'nanjekyejoannah']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue19904'
versions = ['Python 3.6']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
🐛 Bug 🔔 Pending processing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
jumpserver/jumpserver#17584 ·
-
link-check link-check:sphinx-theme
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
modelscope/DiffSynth-Studio#1702 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
qgis/QGIS-Documentation#11275 ·
-
bug priority:normal ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
OpenHands/extensions#626 · 1 comment ·