Inconsistent/incomplete disassembly of methods vs method source code
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 39800 |
|---|---|
| Nosy | @stevendaprano, @sr-murthy |
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-02-29.15:27:53.790>
labels = ['3.7', 'type-bug', 'library']
title = 'Inconsistent/incomplete disassembly of methods vs method source code'
updated_at = <Date 2020-03-01.06:58:53.787>
user = 'https://github.com/sr-murthy'
bugs.python.org fields:
activity = <Date 2020-03-01.06:58:53.787>
actor = 'smurthy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-02-29.15:27:53.790>
creator = 'smurthy'
dependencies = []
files = []
hgrepos = []
issue_num = 39800
keywords = []
message_count = 7.0
messages = ['362985', '362989', '362995', '362997', '363040', '363042', '363043']
nosy_count = 2.0
nosy_names = ['steven.daprano', 'smurthy']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue39800'
versions = ['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
The issue names no files, tests, or entry points. Start by reviewing the linked BPO issue 39800 and its seven-message discussion, then locate the relevant disassembly implementation and tests. Done means the disassembly of methods is consistent and complete relative to their source code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100