ipaddress: Wrong behavior with ::ffff:1.2.3.4 style IPs
Open
Nobody has claimed this yet.
docs
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 27269 |
|---|---|
| Nosy | @socketpair, @ThiefMaster, @arp11 |
| 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 2016-06-08.14:55:23.856>
labels = ['type-bug', 'library', 'docs']
title = 'ipaddress: Wrong behavior with ::ffff:1.2.3.4 style IPs'
updated_at = <Date 2017-05-23.00:08:58.753>
user = 'https://github.com/ThiefMaster'
bugs.python.org fields:
activity = <Date 2017-05-23.00:08:58.753>
actor = 'arp11'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'Library (Lib)']
creation = <Date 2016-06-08.14:55:23.856>
creator = 'ThiefMaster'
dependencies = []
files = []
hgrepos = []
issue_num = 27269
keywords = []
message_count = 4.0
messages = ['267861', '269984', '269986', '294198']
nosy_count = 5.0
nosy_names = ['pmoody', 'docs@python', 'socketpair', 'ThiefMaster', 'arp11']
pr_nums = ['1741']
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue27269'
versions = ['Python 3.5', '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
The issue concerns Python's ipaddress library and references BPO issue 27269; start by reading that issue and reviewing PR 1741, which is listed as existing work. Confirm the intended behavior for ::ffff:1.2.3.4-style addresses and verify the result with the relevant project tests.
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
- 25/100