Generic script for finding bugs in get_source_segment
Open
Nobody has claimed this yet.
3.8 (EOL)
3.9 (EOL)
interpreter-core
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 39810 |
|---|---|
| Nosy | @ilevkivskyi, @alexmojaki |
| 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 2020-03-01.11:59:05.328>
labels = ['interpreter-core', 'type-bug', '3.8', '3.9']
title = 'Generic script for finding bugs in get_source_segment'
updated_at = <Date 2020-03-06.19:19:01.611>
user = 'https://github.com/alexmojaki'
bugs.python.org fields:
activity = <Date 2020-03-06.19:19:01.611>
actor = 'levkivskyi'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2020-03-01.11:59:05.328>
creator = 'alexmojaki'
dependencies = []
files = ['48940']
hgrepos = []
issue_num = 39810
keywords = []
message_count = 1.0
messages = ['363056']
nosy_count = 2.0
nosy_names = ['levkivskyi', 'alexmojaki']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue39810'
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 get_source_segment_test.py, the only file linked in the issue, and identify how it exercises get_source_segment. Determine the intended scope of a generic bug-finding script from the existing test and issue context. Done would be a usable script with a clear way to demonstrate or test the bugs it finds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100