Solve IPv4 categorisation issues with the ipaddress module

Open
#82,931 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
networking

Research direction

The issue metadata identifies Python's ipaddress module and the original bug tracker entry, but it names no source files, tests, or specific categorisation cases. Start by reviewing the linked BPO issue and the ipaddress library implementation and tests. Done means resolving the reported IPv4 categorisation behavior with corresponding test coverage.

Written by the indexing model from the issue text.

Description

3.9 (EOL) stdlib type-bug
BPO 38750
Nosy @JamoBox

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 2019-11-08.21:06:11.802>
labels = ['type-bug', 'library', '3.9']
title = 'Solve IPv4 categorisation issues with the ipaddress module'
updated_at = <Date 2020-01-01.08:39:08.606>
user = 'https://github.com/JamoBox'

bugs.python.org fields:

activity = <Date 2020-01-01.08:39:08.606>
actor = 'samjonas'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-11-08.21:06:11.802>
creator = 'Wicken'
dependencies = []
files = []
hgrepos = []
issue_num = 38750
keywords = []
message_count = 3.0
messages = ['356265', '356267', '359148']
nosy_count = 3.0
nosy_names = ['pmoody', 'samjonas', 'Wicken']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue38750'
versions = ['Python 3.9']

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.