Make objects with empty __slots__ GC types
Open
Nobody has claimed this yet.
3.7 (EOL)
interpreter-core
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 28651 |
|---|---|
| Nosy | @gvanrossum, @vstinner, @serhiy-storchaka, @1st1, @ilevkivskyi |
| 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 2016-11-09.18:31:45.543>
labels = ['interpreter-core', '3.7']
title = 'Make objects with empty __slots__ GC types'
updated_at = <Date 2017-01-23.11:03:08.160>
user = 'https://github.com/1st1'
bugs.python.org fields:
activity = <Date 2017-01-23.11:03:08.160>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2016-11-09.18:31:45.543>
creator = 'yselivanov'
dependencies = []
files = ['45412']
hgrepos = []
issue_num = 28651
keywords = ['patch']
message_count = 4.0
messages = ['280427', '280435', '280445', '286072']
nosy_count = 5.0
nosy_names = ['gvanrossum', 'vstinner', 'serhiy.storchaka', 'yselivanov', 'levkivskyi']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue28651'
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 reviewing the referenced slots_gc.patch and the issue's Interpreter Core context. Trace how objects with empty slots are classified for garbage collection, then identify the relevant tests or add coverage for the requested behavior. Done means such objects are treated as GC types without regressing existing object-layout behavior.
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
- Mostly clear
- Newbie friendliness
- 30/100