Unpickling objects with recursive references and partials fail due to incomplete state passed to __setstate__
Open
Nobody has claimed this yet.
interpreter-core
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 33249 |
|---|---|
| Nosy | @aleneum |
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-04-09.12:37:25.064>
labels = ['interpreter-core', 'type-bug']
title = 'Unpickling objects with recursive references and partials fail due to incomplete state passed to __setstate__'
updated_at = <Date 2018-04-09.15:31:56.040>
user = 'https://github.com/aleneum'
bugs.python.org fields:
activity = <Date 2018-04-09.15:31:56.040>
actor = 'aleneum'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2018-04-09.12:37:25.064>
creator = 'aleneum'
dependencies = []
files = []
hgrepos = []
issue_num = 33249
keywords = []
message_count = 2.0
messages = ['315127', '315130']
nosy_count = 1.0
nosy_names = ['aleneum']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue33249'
versions = ['Python 3.4', 'Python 3.5', 'Python 3.6']
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 payload names no files or tests. Start by reproducing the recursive-reference and partials unpickling failure, then trace the CPython interpreter-core unpickling path and its setstate handling. Done means these objects unpickle successfully with complete state passed to setstate, with regression coverage added where appropriate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100