Incorrect shutil.copytree() behaviour with symlinks
Open
Nobody has claimed this yet.
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 47049 |
|---|---|
| Nosy | @vajdaz |
| PRs |
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 2022-03-17.18:50:19.316>
labels = ['type-bug', 'library', '3.11']
title = 'Incorrect shutil.copytree() behaviour with symlinks'
updated_at = <Date 2022-04-04.22:13:23.663>
user = 'https://github.com/vajdaz'
bugs.python.org fields:
activity = <Date 2022-04-04.22:13:23.663>
actor = 'vajdaz'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2022-03-17.18:50:19.316>
creator = 'vajdaz'
dependencies = []
files = []
hgrepos = []
issue_num = 47049
keywords = ['patch']
message_count = 2.0
messages = ['415437', '416700']
nosy_count = 1.0
nosy_names = ['vajdaz']
pr_nums = ['31967']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue47049'
versions = ['Python 3.11']
Linked PRs
- gh-132984
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 at shutil.copytree() and review the issue history, including linked PR gh-132984. Determine the incorrect symlink behavior from the existing discussion and verify the expected behavior with the relevant standard-library tests; done means the reported copytree case behaves correctly without regressions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100