wrong FNAME in tarfile if tgz extension is used
Open
Nobody has claimed this yet.
3.10
3.11
3.9 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 44495 |
|---|---|
| Nosy | @veaviticus |
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-06-23.06:55:14.378>
labels = ['type-bug', 'library', '3.9', '3.10', '3.11']
title = 'wrong FNAME in tarfile if tgz extension is used'
updated_at = <Date 2022-01-16.17:58:03.979>
user = 'https://bugs.python.org/maciejmmmisiak'
bugs.python.org fields:
activity = <Date 2022-01-16.17:58:03.979>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-06-23.06:55:14.378>
creator = 'maciej.mm.misiak'
dependencies = []
files = []
hgrepos = []
issue_num = 44495
keywords = []
message_count = 2.0
messages = ['396382', '405468']
nosy_count = 2.0
nosy_names = ['veaviticus', 'maciej.mm.misiak']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue44495'
versions = ['Python 3.9', 'Python 3.10', '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 in Python's standard-library tarfile implementation under Lib/ and reproduce the reported behavior when a .tgz extension is used. Confirm the expected FNAME value and add or update coverage for that case; no specific test file is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100