Deprecate the zlib decompressor’s flush() method
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start with the linked deprecate-flush.v2.patch and compare it with deprecate-flush.patch and max_length.patch to understand the proposed zlib decompressor flush() change. Check the Python 3.6 target and the existing patch-review discussion; done means the deprecation is implemented consistently with the accepted proposal and its relevant tests pass.
Written by the indexing model from the issue text.
Description
| BPO | 23200 |
|---|---|
| Nosy | @vadmium, @serhiy-storchaka |
| 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 2015-01-09.01:26:21.340>
labels = ['type-feature', 'library']
title = 'Deprecate the zlib decompressor\xe2\x80\x99s flush() method'
updated_at = <Date 2016-02-02.11:33:17.625>
user = 'https://github.com/vadmium'
bugs.python.org fields:
activity = <Date 2016-02-02.11:33:17.625>
actor = 'martin.panter'
assignee = 'nadeem.vawda'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2015-01-09.01:26:21.340>
creator = 'martin.panter'
dependencies = []
files = ['37650', '41067', '41780']
hgrepos = []
issue_num = 23200
keywords = ['patch']
message_count = 9.0
messages = ['233709', '233710', '254828', '254836', '254837', '254841', '255564', '256142', '259380']
nosy_count = 5.0
nosy_names = ['nadeem.vawda', 'docs@python', 'python-dev', 'martin.panter', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue23200'
versions = ['Python 3.6']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100