[RFE] tarfile: add an option to change the "blocking factor"
Open
Nobody has claimed this yet.
3.8 (EOL)
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 31774 |
|---|---|
| Nosy | @gustaebel, @vstinner, @stratakis, @nitishch |
| 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 2017-10-12.14:17:19.775>
labels = ['3.8', 'type-feature', 'library']
title = '[RFE] tarfile: add an option to change the "blocking factor"'
updated_at = <Date 2018-06-20.13:04:55.361>
user = 'https://github.com/stratakis'
bugs.python.org fields:
activity = <Date 2018-06-20.13:04:55.361>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-10-12.14:17:19.775>
creator = 'cstratak'
dependencies = []
files = ['47218']
hgrepos = []
issue_num = 31774
keywords = []
message_count = 4.0
messages = ['304241', '304457', '304458', '320075']
nosy_count = 4.0
nosy_names = ['lars.gustaebel', 'vstinner', 'cstratak', 'nitishch']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue31774'
versions = ['Python 3.8']
Linked PRs
- gh-129260
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 reading the tarfile implementation and the uploaded tartest.py file, then inspect linked PR gh-129260 for the current work. Determine how a configurable blocking factor should affect archive handling and verify the behavior with tarfile tests; done means the option is implemented and its expected behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100