Restore default implementation of __ne__ in mixins Set and Mapping
Open
Nobody has claimed this yet.
3.10
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 41416 |
|---|---|
| Nosy | @rhettinger, @serhiy-storchaka |
| 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 2020-07-28.06:34:53.290>
labels = ['type-bug', 'library', '3.10']
title = 'Restore default implementation of __ne__ in mixins Set and Mapping'
updated_at = <Date 2022-01-29.22:36:18.887>
user = 'https://github.com/serhiy-storchaka'
bugs.python.org fields:
activity = <Date 2022-01-29.22:36:18.887>
actor = 'serhiy.storchaka'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-07-28.06:34:53.290>
creator = 'serhiy.storchaka'
dependencies = []
files = []
hgrepos = []
issue_num = 41416
keywords = ['patch']
message_count = 2.0
messages = ['374470', '374549']
nosy_count = 2.0
nosy_names = ['rhettinger', 'serhiy.storchaka']
pr_nums = ['21628']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue41416'
versions = ['Python 3.10']
Linked PRs
- gh-141366
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 reviewing linked PR gh-141366 and the earlier PR #21628, which address restoring the default ne implementation in the Set and Mapping mixins. Confirm the intended behavior and relevant tests there; done means the requested implementation is complete and the tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100