recv returning 0 on closed connection not documented
Open
Nobody has claimed this yet.
docs
topic-socket
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 33121 |
|---|---|
| Nosy | @terryjreedy, @taleinat |
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-03-22.14:15:08.896>
labels = ['type-feature', 'docs']
title = 'recv returning 0 on closed connection not documented'
updated_at = <Date 2018-07-25.18:11:20.185>
user = 'https://bugs.python.org/joders'
bugs.python.org fields:
activity = <Date 2018-07-25.18:11:20.185>
actor = 'taleinat'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2018-03-22.14:15:08.896>
creator = 'joders'
dependencies = []
files = []
hgrepos = []
issue_num = 33121
keywords = []
message_count = 3.0
messages = ['314260', '314352', '322380']
nosy_count = 4.0
nosy_names = ['terry.reedy', 'taleinat', 'docs@python', 'joders']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue33121'
versions = ['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 by locating the Python socket documentation for recv and reviewing how a closed connection is currently described. Document that recv returns 0 when the connection is closed, and verify the wording against the behavior described by the issue.
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
- 35/100