split existing optimization levels into granular options
Open
Nobody has claimed this yet.
interpreter-core
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 33501 |
|---|---|
| Nosy | @brettcannon, @ncoghlan, @vstinner, @carljm, @stevendaprano, @ambv, @ericsnowcurrently, @serhiy-storchaka |
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 2018-05-14.16:18:37.204>
labels = ['type-feature']
title = 'split existing optimization levels into granular options'
updated_at = <Date 2018-05-19.00:36:17.649>
user = 'https://github.com/carljm'
bugs.python.org fields:
activity = <Date 2018-05-19.00:36:17.649>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2018-05-14.16:18:37.204>
creator = 'carljm'
dependencies = []
files = []
hgrepos = []
issue_num = 33501
keywords = []
message_count = 6.0
messages = ['316531', '316544', '316905', '316908', '316926', '317080']
nosy_count = 8.0
nosy_names = ['brett.cannon', 'ncoghlan', 'vstinner', 'carljm', 'steven.daprano', 'lukasz.langa', 'eric.snow', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue33501'
versions = []
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 the linked BPO issue 33501 and its discussion, since no source files, tests, or entry points are identified here. Define the desired granular optimization options and their behavior from that discussion; done means the existing optimization levels are split into the agreed options with coverage for their behavior.
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