socket.getaddrinfo() should return named tuples
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- networking
Research direction
Start by reading the issue's linked getaddrinfo.patch and locating the socket.getaddrinfo() implementation and its tests. Compare the proposed behavior with the existing return values; done means the function returns named tuples while preserving the requested API behavior and the relevant tests pass.
Written by the indexing model from the issue text.
Description
| BPO | 8881 |
|---|---|
| Nosy | @pitrou, @vstinner, @ericvsmith, @giampaolo, @florentx, @csabella |
| Files |
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 2010-06-02.21:31:26.791>
labels = ['type-feature', 'library']
title = 'socket.getaddrinfo() should return named tuples'
updated_at = <Date 2018-01-27.18:31:22.586>
user = 'https://github.com/giampaolo'
bugs.python.org fields:
activity = <Date 2018-01-27.18:31:22.586>
actor = 'cheryl.sabella'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2010-06-02.21:31:26.791>
creator = 'giampaolo.rodola'
dependencies = []
files = ['26287']
hgrepos = []
issue_num = 8881
keywords = ['patch']
message_count = 6.0
messages = ['106916', '106919', '151200', '151201', '164816', '310874']
nosy_count = 8.0
nosy_names = ['exarkun', 'pitrou', 'vstinner', 'eric.smith', 'giampaolo.rodola', 'flub', 'flox', 'cheryl.sabella']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue8881'
versions = ['Python 3.4']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100