dis.Bytecode objects should be comparable
Open
Nobody has claimed this yet.
3.9 (EOL)
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 39902 |
|---|---|
| Nosy | @stevendaprano, @isidentical |
| 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-03-08.12:15:59.621>
labels = ['type-feature', 'library', '3.9']
title = 'dis.Bytecode objects should be comparable'
updated_at = <Date 2020-03-08.14:01:08.976>
user = 'https://github.com/isidentical'
bugs.python.org fields:
activity = <Date 2020-03-08.14:01:08.976>
actor = 'BTaskaya'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-03-08.12:15:59.621>
creator = 'BTaskaya'
dependencies = []
files = []
hgrepos = []
issue_num = 39902
keywords = ['patch']
message_count = 3.0
messages = ['363656', '363661', '363663']
nosy_count = 2.0
nosy_names = ['steven.daprano', 'BTaskaya']
pr_nums = ['18849']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue39902'
versions = ['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 with the dis.Bytecode entry point and review the existing python/cpython#18849 pull request, which is listed in the issue history. Confirm the intended comparison behavior and whether it is already covered before changing anything; done means the requested comparability is implemented and verified by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100