bz2: BZ2File should expose compression level as an attribute
Open
Nobody has claimed this yet.
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 27450 |
|---|---|
| Nosy | @bitdancer, @vadmium, @zhangyangyu |
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-07-04.20:01:33.695>
labels = ['type-feature', 'library']
title = 'bz2: BZ2File should expose compression level as an attribute'
updated_at = <Date 2016-09-04.08:33:02.244>
user = 'https://bugs.python.org/joshtriplett'
bugs.python.org fields:
activity = <Date 2016-09-04.08:33:02.244>
actor = 'joshtriplett'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2016-07-04.20:01:33.695>
creator = 'joshtriplett'
dependencies = []
files = []
hgrepos = []
issue_num = 27450
keywords = []
message_count = 5.0
messages = ['269806', '269818', '272756', '274348', '274349']
nosy_count = 4.0
nosy_names = ['joshtriplett', 'r.david.murray', 'martin.panter', 'xiang.zhang']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue27450'
versions = ['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
Start at the bz2.BZ2File entry point and inspect how compression settings are represented. Identify the relevant standard-library tests and update coverage so the compression level is exposed as an attribute; done means the attribute is available and its behavior is tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100