Inconsistent calls to __eq__ from built-in __contains__
Open
Nobody has claimed this yet.
3.8 (EOL)
3.9 (EOL)
docs
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 27605 |
|---|---|
| Nosy | @rhettinger, @terryjreedy, @stevendaprano, @bitdancer |
| Files |
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-07-24.12:13:15.023>
labels = ['type-bug', '3.8', '3.9', 'docs']
title = 'Inconsistent calls to __eq__ from built-in __contains__'
updated_at = <Date 2019-05-30.20:41:50.346>
user = 'https://bugs.python.org/vfaronov'
bugs.python.org fields:
activity = <Date 2019-05-30.20:41:50.346>
actor = 'cheryl.sabella'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2016-07-24.12:13:15.023>
creator = 'vfaronov'
dependencies = []
files = ['43857']
hgrepos = []
issue_num = 27605
keywords = []
message_count = 5.0
messages = ['271145', '271154', '271158', '271165', '271640']
nosy_count = 6.0
nosy_names = ['rhettinger', 'terry.reedy', 'steven.daprano', 'r.david.murray', 'docs@python', 'vfaronov']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue27605'
versions = ['Python 3.8', 'Python 3.9']
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 reading the contains_eq.py example linked in the issue and compare its behavior with the relevant built-in contains and eq documentation. Determine which inconsistent behavior needs to be documented or clarified, then verify that the resulting documentation explains the observed calls consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100