shutil.copytree(symlinks=True) fails when copying symlinks cross-device and there is no alternative
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 29516 |
|---|---|
| Nosy | @darko-poljak |
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 2017-02-09.21:12:34.636>
labels = ['3.7', 'type-bug', 'library']
title = 'shutil.copytree(symlinks=True) fails when copying symlinks cross-device and there is no alternative'
updated_at = <Date 2018-07-11.07:46:05.806>
user = 'https://github.com/darko-poljak'
bugs.python.org fields:
activity = <Date 2018-07-11.07:46:05.806>
actor = 'serhiy.storchaka'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-02-09.21:12:34.636>
creator = 'poljakowski'
dependencies = []
files = []
hgrepos = []
issue_num = 29516
keywords = []
message_count = 1.0
messages = ['287455']
nosy_count = 1.0
nosy_names = ['poljakowski']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue29516'
versions = ['Python 3.3', 'Python 3.4', 'Python 3.5', 'Python 3.6', 'Python 3.7']
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 trace its symlink handling when the source and destination are on different devices. Reproduce the reported failure and inspect the available copy behavior; done means copytree(symlinks=True) handles this case without failing when an alternative is available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100