exception text is being sourced from the wrong file
Open
Nobody has claimed this yet.
interpreter-core
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 36259 |
|---|---|
| Nosy | @stevendaprano, @tirkarthi, @jessefarnham |
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 2019-03-11.01:51:16.936>
labels = ['3.8', 'type-bug', '3.7']
title = 'exception text is being sourced from the wrong file'
updated_at = <Date 2019-04-07.19:04:59.497>
user = 'https://bugs.python.org/rhubarbdogx'
bugs.python.org fields:
activity = <Date 2019-04-07.19:04:59.497>
actor = 'jesse.farnham'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2019-03-11.01:51:16.936>
creator = 'rhubarbdog x'
dependencies = []
files = []
hgrepos = []
issue_num = 36259
keywords = []
message_count = 4.0
messages = ['337642', '337647', '339581', '339582']
nosy_count = 4.0
nosy_names = ['steven.daprano', 'xtreak', 'jesse.farnham', 'rhubarbdog x']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue36259'
versions = ['Python 2.7', 'Python 3.7', 'Python 3.8']
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 mentions no source files, tests, or entry points, so begin by reviewing the linked BPO issue 36259 and locating the code that produces the affected exception text. Done means identifying and correcting the file source, with a regression test demonstrating the exception text comes from the intended file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100