Implementing sub-generation steps in the gc
Open
Nobody has claimed this yet.
3.9 (EOL)
interpreter-core
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 39143 |
|---|---|
| Nosy | @tim-one, @nascheme, @pablogsal, @nanjekyejoannah |
| 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 2019-12-27.21:35:04.084>
labels = ['interpreter-core', 'type-feature', '3.9']
title = 'Implementing sub-generation steps in the gc'
updated_at = <Date 2019-12-29.03:52:57.177>
user = 'https://github.com/pablogsal'
bugs.python.org fields:
activity = <Date 2019-12-29.03:52:57.177>
actor = 'pablogsal'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2019-12-27.21:35:04.084>
creator = 'pablogsal'
dependencies = []
files = ['48807', '48808']
hgrepos = []
issue_num = 39143
keywords = []
message_count = 16.0
messages = ['358916', '358947', '358949', '358950', '358951', '358955', '358958', '358959', '358960', '358962', '358963', '358971', '358972', '358973', '358976', '358977']
nosy_count = 4.0
nosy_names = ['tim.peters', 'nascheme', 'pablogsal', 'nanjekyejoannah']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue39143'
versions = ['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 reviewing the linked BPO issue 39143 and the attached vanilla-vs-buffered.png and diff-vanilla-buffered.png files. The issue does not name implementation files, tests, or a concrete completion criterion, so clarify the intended sub-generation behavior and scope before selecting an entry point or defining what done means.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100