addTypeEqualityFunc is not used in assertListEqual
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
Research direction
Start by locating the unittest entry points named in the issue, addTypeEqualityFunc and assertListEqual, then inspect the existing unittest tests around equality assertions. Done means assertListEqual honors a registered type equality function and regression coverage demonstrates that behavior.
Written by the indexing model from the issue text.
Description
| BPO | 22452 |
|---|---|
| Nosy | @pitrou, @rbtcollins, @ezio-melotti, @bitdancer, @voidspace, @serhiy-storchaka, @swarmer, @iritkatriel |
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 2014-09-21.11:12:08.725>
labels = ['type-feature', 'library', '3.11']
title = 'addTypeEqualityFunc is not used in assertListEqual'
updated_at = <Date 2021-08-07.19:03:47.609>
user = 'https://bugs.python.org/simonzack'
bugs.python.org fields:
activity = <Date 2021-08-07.19:03:47.609>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2014-09-21.11:12:08.725>
creator = 'simonzack'
dependencies = []
files = []
hgrepos = []
issue_num = 22452
keywords = []
message_count = 6.0
messages = ['227210', '227212', '227222', '230776', '230785', '399199']
nosy_count = 9.0
nosy_names = ['pitrou', 'rbcollins', 'ezio.melotti', 'r.david.murray', 'michael.foord', 'serhiy.storchaka', 'anton.barkovsky', 'simonzack', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue22452'
versions = ['Python 3.11']
- 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