CField.size from the ctypes module does not behave as documented on bitfields
Open
Nobody has claimed this yet.
docs
topic-ctypes
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 37187 |
|---|---|
| Nosy | @amauryfa, @abalkin, @meadori, @mangrisano, @shihai1991 |
| PRs |
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 2019-06-07.03:46:36.822>
labels = ['ctypes', 'type-bug', 'docs']
title = 'CField.size from the ctypes module does not behave as documented on bitfields'
updated_at = <Date 2019-07-08.17:32:40.963>
user = 'https://bugs.python.org/EricWieser'
bugs.python.org fields:
activity = <Date 2019-07-08.17:32:40.963>
actor = 'shihai1991'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'ctypes']
creation = <Date 2019-06-07.03:46:36.822>
creator = 'Eric Wieser'
dependencies = []
files = []
hgrepos = []
issue_num = 37187
keywords = ['patch']
message_count = 2.0
messages = ['344895', '344921']
nosy_count = 7.0
nosy_names = ['amaury.forgeotdarc', 'belopolsky', 'meador.inge', 'docs@python', 'Eric Wieser', 'mangrisano', 'shihai1991']
pr_nums = ['14647']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue37187'
versions = []
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 ctypes module documentation and review PR #14647, the only implementation reference named in the issue. Compare CField.size's documented behavior on bitfields with its current behavior; done means the documentation and behavior agree.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100