tarfile: add support for creating an archive of potentially changing files
Open
Nobody has claimed this yet.
3.11
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 44899 |
|---|---|
| Nosy | @ethanfurman, @marko-tuononen |
| PRs | |
| 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 2021-08-12.11:43:12.867>
labels = ['type-feature', 'library', '3.11']
title = 'tarfile: add support for creating an archive of potentially changing files'
updated_at = <Date 2022-01-06.08:16:54.910>
user = 'https://github.com/marko-tuononen'
bugs.python.org fields:
activity = <Date 2022-01-06.08:16:54.910>
actor = 'marko-tuononen'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-08-12.11:43:12.867>
creator = 'marko-tuononen'
dependencies = []
files = ['50412']
hgrepos = []
issue_num = 44899
keywords = ['patch']
message_count = 2.0
messages = ['399443', '405303']
nosy_count = 2.0
nosy_names = ['ethan.furman', 'marko-tuononen']
pr_nums = ['30402', '30426']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue44899'
versions = ['Python 3.11']
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 the attached tarfile_ut.py unit test, then inspect the tarfile library implementation and the referenced pull requests. Reproduce the changing-files case and use the test to determine the expected archive behavior; done means the case is supported and the relevant tests pass.
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
- Mostly clear
- Newbie friendliness
- 25/100