compile(mode='eval') uninformative error message
Open
Nobody has claimed this yet.
interpreter-core
topic-parser
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 38131 |
|---|---|
| Nosy | @benjaminp, @ikamensh, @pablogsal, @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 2019-09-12.10:21:59.042>
labels = ['interpreter-core', '3.9']
title = "compile(mode='eval') uninformative error message"
updated_at = <Date 2020-05-07.15:16:43.409>
user = 'https://github.com/ikamensh'
bugs.python.org fields:
activity = <Date 2020-05-07.15:16:43.409>
actor = 'BTaskaya'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2019-09-12.10:21:59.042>
creator = 'Ilya Kamenshchikov'
dependencies = []
files = []
hgrepos = []
issue_num = 38131
keywords = ['patch']
message_count = 3.0
messages = ['352090', '358905', '368351']
nosy_count = 4.0
nosy_names = ['benjamin.peterson', 'Ilya Kamenshchikov', 'pablogsal', 'BTaskaya']
pr_nums = ['17715']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue38131'
versions = ['Python 3.9']
Linked PRs
- gh-150912
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
Review linked PR gh-150912 and the compile(mode='eval') entry point first. Confirm the current error and use the PR's expectations to determine whether the message is informative; done means the reported compile error communicates the relevant cause.
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
- 20/100