Deprecate readinto() fallback path in _pickle.c
Open
Nobody has claimed this yet.
3.13
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 39734 |
|---|---|
| Nosy | @pitrou, @ZackerySpytz, @pierreglaser |
| PRs |
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 2020-02-23.22:47:08.376>
labels = ['type-feature', 'library', '3.9']
title = 'Deprecate readinto() fallback path in _pickle.c'
updated_at = <Date 2020-03-30.22:10:26.404>
user = 'https://github.com/pitrou'
bugs.python.org fields:
activity = <Date 2020-03-30.22:10:26.404>
actor = 'ZackerySpytz'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-02-23.22:47:08.376>
creator = 'pitrou'
dependencies = []
files = []
hgrepos = []
issue_num = 39734
keywords = ['patch']
message_count = 1.0
messages = ['362547']
nosy_count = 4.0
nosy_names = ['pitrou', 'ogrisel', 'ZackerySpytz', 'pierreglaser']
pr_nums = ['19237']
priority = 'low'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue39734'
versions = ['Python 3.9']
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 with _pickle.c and the linked PR #19237, which are the issue's only implementation references. Determine the scope of the readinto() fallback deprecation and its required tests; done means the fallback path is deprecated as requested and the relevant checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100