tarfile: unexpected IsADirectoryError on extraction
Open
Nobody has claimed this yet.
3.7 (EOL)
3.8 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 36986 |
|---|---|
| Nosy | @alter-bug-tracer |
| 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 2019-05-21.07:13:29.170>
labels = ['3.8', 'type-bug', '3.7']
title = 'tarfile: unexpected IsADirectoryError on extraction'
updated_at = <Date 2019-06-02.22:04:23.111>
user = 'https://github.com/alter-bug-tracer'
bugs.python.org fields:
activity = <Date 2019-06-02.22:04:23.111>
actor = 'mangrisano'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2019-05-21.07:13:29.170>
creator = 'alter-bug-tracer'
dependencies = []
files = ['48341']
hgrepos = []
issue_num = 36986
keywords = []
message_count = 2.0
messages = ['342983', '343005']
nosy_count = 1.0
nosy_names = ['alter-bug-tracer']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue36986'
versions = ['Python 3.6', 'Python 3.7', 'Python 3.8']
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 tarfile extraction entry points and reproduce the report using the attached input0.tar archive and the BPO issue 36986 details. Determine why extraction raises IsADirectoryError unexpectedly, then add a regression test showing the expected extraction behavior.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100