Explicitly mention bytes and other buffers in the documentation for float()
Open
Nobody has claimed this yet.
docs
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 33567 |
|---|---|
| Nosy | @rhettinger, @mjpieters, @joelthelion |
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 2018-05-18.10:41:41.124>
labels = ['3.11', 'type-feature', '3.9', '3.10', 'docs']
title = 'Explicitly mention bytes and other buffers in the documentation for float()'
updated_at = <Date 2021-12-19.04:18:07.710>
user = 'https://github.com/mjpieters'
bugs.python.org fields:
activity = <Date 2021-12-19.04:18:07.710>
actor = 'rhettinger'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2018-05-18.10:41:41.124>
creator = 'mjpieters'
dependencies = []
files = []
hgrepos = []
issue_num = 33567
keywords = []
message_count = 1.0
messages = ['317022']
nosy_count = 4.0
nosy_names = ['rhettinger', 'mjpieters', 'docs@python', 'joelthelion']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue33567'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
Linked PRs
- gh-155501
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 documentation for the built-in float() function and review how accepted input types are described. Done means the documentation explicitly mentions bytes and other buffer objects; the issue lists linked PR gh-155501, so check that work before starting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 30/100