shutil.make_archive (xxx, tar, root_dir) is adding './' entry to archive which is wrong
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
Research direction
Reproduce the archive contents using the attached tarfile_test.tar, then inspect shutil.make_archive with tar and root_dir handling. Done means the generated archive no longer contains an unwanted './' entry; an existing linked PR should also be reviewed for prior work.
Written by the indexing model from the issue text.
Description
| BPO | 35964 |
|---|---|
| Nosy | @Yhg1s, @tarekziade, @SpecLad, @serhiy-storchaka, @websurfer5 |
| 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 2019-02-11.12:40:46.518>
labels = ['3.7', 'library']
title = "shutil.make_archive (xxx, tar, root_dir) is adding './' entry to archive which is wrong"
updated_at = <Date 2019-08-27.20:46:19.371>
user = 'https://bugs.python.org/HFM'
bugs.python.org fields:
activity = <Date 2019-08-27.20:46:19.371>
actor = 'SpecLad'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-02-11.12:40:46.518>
creator = 'HFM'
dependencies = []
files = ['48132']
hgrepos = []
issue_num = 35964
keywords = ['patch']
message_count = 2.0
messages = ['335211', '344254']
nosy_count = 10.0
nosy_names = ['twouters', 'alanmcintyre', 'bialix', 'tarek', 'python-dev', 'SpecLad', 'serhiy.storchaka', 'HFM', 'Oskar Persson', 'Jeffrey.Kintscher']
pr_nums = ['13738']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue35964'
versions = ['Python 2.7', 'Python 3.6', 'Python 3.7']
Linked PRs
- gh-118152
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
🐛 Bug 🔔 Pending processing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
jumpserver/jumpserver#17584 ·