Emit ResourceWarning when implicitly terminating a suspended frame?
Open
Nobody has claimed this yet.
3.7 (EOL)
interpreter-core
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 28629 |
|---|---|
| Nosy | @ncoghlan, @vstinner, @njsmith, @vadmium, @1st1, @jstasiak |
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 2016-11-07.02:50:31.347>
labels = ['3.7', 'performance']
title = 'Emit ResourceWarning when implicitly terminating a suspended frame?'
updated_at = <Date 2017-07-19.09:12:49.442>
user = 'https://github.com/ncoghlan'
bugs.python.org fields:
activity = <Date 2017-07-19.09:12:49.442>
actor = 'jstasiak'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2016-11-07.02:50:31.347>
creator = 'ncoghlan'
dependencies = []
files = []
hgrepos = []
issue_num = 28629
keywords = []
message_count = 11.0
messages = ['280185', '280189', '280193', '280200', '280728', '280736', '280737', '280738', '280752', '280762', '290953']
nosy_count = 6.0
nosy_names = ['ncoghlan', 'vstinner', 'njs', 'martin.panter', 'yselivanov', 'jstasiak']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'resource usage'
url = 'https://bugs.python.org/issue28629'
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
Start by reading BPO issue 28629 and its 11-message discussion, since no source file, test, or entry point is identified. Clarify the expected behavior for implicitly terminating a suspended frame and determine what evidence would show that the requested ResourceWarning behavior is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100