sock.proto does not reflect actual protocol
Open
Nobody has claimed this yet.
3.13
extension-modules
topic-socket
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 27816 |
|---|---|
| Nosy | @tiran, @vadmium |
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-08-20.16:21:59.357>
labels = ['extension-modules', 'type-bug', '3.9', '3.10', '3.11']
title = 'sock.proto does not reflect actual protocol'
updated_at = <Date 2021-10-21.11:59:38.772>
user = 'https://github.com/tiran'
bugs.python.org fields:
activity = <Date 2021-10-21.11:59:38.772>
actor = 'christian.heimes'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Extension Modules']
creation = <Date 2016-08-20.16:21:59.357>
creator = 'christian.heimes'
dependencies = []
files = []
hgrepos = []
issue_num = 27816
keywords = []
message_count = 3.0
messages = ['273222', '273250', '404587']
nosy_count = 2.0
nosy_names = ['christian.heimes', 'martin.panter']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue27816'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
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 sock.proto and comparing its declarations with the actual socket protocol behavior in the relevant extension module. The issue provides no file path, failing test, or precise mismatch, so confirm the intended protocol and define a reproducible test before determining what completion means.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100