Readd __index__ support on ipaddress objects
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 28767 |
|---|---|
| Nosy | @ncoghlan, @benjaminp, @serhiy-storchaka, @MojoVampire |
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-11-21.17:40:40.519>
labels = ['3.7']
title = 'Readd __index__ support on ipaddress objects'
updated_at = <Date 2017-03-22.02:01:09.175>
user = 'https://github.com/MojoVampire'
bugs.python.org fields:
activity = <Date 2017-03-22.02:01:09.175>
actor = 'josh.r'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2016-11-21.17:40:40.519>
creator = 'josh.r'
dependencies = []
files = []
hgrepos = []
issue_num = 28767
keywords = []
message_count = 3.0
messages = ['281384', '281385', '289959']
nosy_count = 4.0
nosy_names = ['ncoghlan', 'benjamin.peterson', 'serhiy.storchaka', 'josh.r']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue28767'
versions = ['Python 3.4', 'Python 3.5', 'Python 3.6', '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 with the ipaddress object implementation and the linked BPO issue to understand the requested compatibility and historical behavior. Done means index support is restored for the intended Python versions and the behavior is covered by appropriate tests.
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
- Mostly clear
- Newbie friendliness
- 35/100