C implementation of parts of copy.deepcopy
Open
Nobody has claimed this yet.
3.12
extension-modules
performance
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 28607 |
|---|---|
| Nosy | @villemoes, @pablogsal |
| 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-03.23:11:36.119>
labels = ['extension-modules', '3.7', 'performance']
title = 'C implementation of parts of copy.deepcopy'
updated_at = <Date 2019-01-20.21:43:41.055>
user = 'https://github.com/villemoes'
bugs.python.org fields:
activity = <Date 2019-01-20.21:43:41.055>
actor = 'pablogsal'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Extension Modules']
creation = <Date 2016-11-03.23:11:36.119>
creator = 'villemoes'
dependencies = []
files = ['45344', '45400']
hgrepos = []
issue_num = 28607
keywords = ['patch']
message_count = 3.0
messages = ['280032', '280360', '334105']
nosy_count = 2.0
nosy_names = ['villemoes', 'pablogsal']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = 'performance'
url = 'https://bugs.python.org/issue28607'
versions = ['Python 3.7']
- PR: gh-91610
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 deepcopy.patch files and PR gh-91610, then inspect the existing copy.deepcopy implementation and the issue's test-needed status. Done means the proposed C implementation is integrated without regressions and its behavior is covered by the relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, python
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100