getaddrinfo invalid port number
Open
Nobody has claimed this yet.
3.7 (EOL)
extension-modules
topic-socket
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 30711 |
|---|---|
| Nosy | @smejkar |
| PRs |
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 2017-06-20.13:26:15.605>
labels = ['extension-modules', 'type-bug', '3.7']
title = 'getaddrinfo invalid port number'
updated_at = <Date 2017-06-27.11:24:31.770>
user = 'https://github.com/smejkar'
bugs.python.org fields:
activity = <Date 2017-06-27.11:24:31.770>
actor = 'smejkar'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Extension Modules']
creation = <Date 2017-06-20.13:26:15.605>
creator = 'smejkar'
dependencies = []
files = []
hgrepos = []
issue_num = 30711
keywords = ['patch']
message_count = 3.0
messages = ['296423', '296737', '297021']
nosy_count = 1.0
nosy_names = ['smejkar']
pr_nums = ['2436']
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue30711'
versions = ['Python 3.7']
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 getaddrinfo entry point and reviewing the behavior for invalid port numbers in the extension-module implementation. Reproduce the reported case and identify the existing regression-test area; done means invalid ports are handled consistently and the behavior is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100