Clarify that the (...) convertor to PyArg_ParseTuple... accepts any sequence.
Open
Nobody has claimed this yet.
docs
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 35874 |
|---|---|
| Nosy | @serhiy-storchaka, @anntzer |
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-02-01.09:03:29.813>
labels = ['docs']
title = 'Clarify that the (...) convertor to PyArg_ParseTuple... accepts any sequence.'
updated_at = <Date 2019-02-14.16:59:26.001>
user = 'https://github.com/anntzer'
bugs.python.org fields:
activity = <Date 2019-02-14.16:59:26.001>
actor = 'serhiy.storchaka'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2019-02-01.09:03:29.813>
creator = 'Antony.Lee'
dependencies = []
files = []
hgrepos = []
issue_num = 35874
keywords = []
message_count = 2.0
messages = ['334660', '335546']
nosy_count = 3.0
nosy_names = ['docs@python', 'serhiy.storchaka', 'Antony.Lee']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue35874'
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
Locate the Python C API documentation for the converters used with PyArg_ParseTuple and read the existing wording around sequence arguments. Clarify that the relevant converter accepts any sequence, then verify the documentation accurately reflects the API behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100