ShareableList memory bloat and performance improvement
Open
Nobody has claimed this yet.
3.12
performance
stdlib
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 46799 |
|---|---|
| Nosy | @pitrou, @applio, @tcl326 |
| PRs | |
| 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 2022-02-19.12:02:30.688>
labels = ['3.11', 'library', '3.9', '3.10', 'performance']
title = 'ShareableList memory bloat and performance improvement'
updated_at = <Date 2022-03-27.13:33:18.272>
user = 'https://github.com/tcl326'
bugs.python.org fields:
activity = <Date 2022-03-27.13:33:18.272>
actor = 'tcl326'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2022-02-19.12:02:30.688>
creator = 'tcl326'
dependencies = []
files = ['50632']
hgrepos = []
issue_num = 46799
keywords = ['patch']
message_count = 3.0
messages = ['413544', '414145', '416124']
nosy_count = 3.0
nosy_names = ['pitrou', 'davin', 'tcl326']
pr_nums = ['31467']
priority = 'normal'
resolution = 'remind'
stage = 'patch review'
status = 'open'
superseder = None
type = 'performance'
url = 'https://bugs.python.org/issue46799'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
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
The issue points to shareable_list.py and PR #31467. Start by reviewing the attached implementation and the existing pull request, then measure ShareableList memory use and performance; done means the reported bloat and performance concerns are addressed with supporting results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100