Document behavior when CDLL is called with None as an argument on POSIX systems
Open
Nobody has claimed this yet.
docs
topic-ctypes
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 27329 |
|---|
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-06-16.04:38:10.383>
labels = ['ctypes', 'type-feature', 'docs']
title = 'Document behavior when CDLL is called with None as an argument on POSIX systems'
updated_at = <Date 2016-06-16.04:48:22.898>
user = 'https://bugs.python.org/JeffreyEsquivelSibaja'
bugs.python.org fields:
activity = <Date 2016-06-16.04:48:22.898>
actor = 'martin.panter'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'ctypes']
creation = <Date 2016-06-16.04:38:10.383>
creator = 'Jeffrey Esquivel Sibaja'
dependencies = []
files = []
hgrepos = []
issue_num = 27329
keywords = []
message_count = 1.0
messages = ['268641']
nosy_count = 2.0
nosy_names = ['docs@python', 'Jeffrey Esquivel Sibaja']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue27329'
versions = ['Python 2.7', 'Python 3.5', 'Python 3.6']
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 at the ctypes.CDLL entry point and inspect its existing documentation for POSIX argument handling. Confirm the documented behavior when None is passed, then update the appropriate ctypes documentation and verify the resulting API documentation describes the behavior clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100