Shouldn't shutil.copyfile replace link in dst with follow_symlinks set?

Open
#78,555 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
operating-systems

Research direction

Start at the shutil.copyfile entry point and review how its follow_symlinks argument interacts with a symlink at the destination. Check the existing shutil tests for copyfile and symlink behavior, then establish the expected replacement behavior and add a regression test that demonstrates it.

Written by the indexing model from the issue text.

Description

3.7 (EOL) stdlib type-bug
BPO 34374
Nosy @bitdancer

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 2018-08-10.17:36:47.595>
labels = ['3.7', 'type-bug', 'library']
title = "Shouldn't shutil.copyfile replace link in dst with follow_symlinks set?"
updated_at = <Date 2020-09-15.06:23:53.390>
user = 'https://bugs.python.org/theger'

bugs.python.org fields:

activity = <Date 2020-09-15.06:23:53.390>
actor = 'Pavel Raiskup'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2018-08-10.17:36:47.595>
creator = 'theger'
dependencies = []
files = []
hgrepos = []
issue_num = 34374
keywords = []
message_count = 3.0
messages = ['323373', '323374', '376928']
nosy_count = 3.0
nosy_names = ['r.david.murray', 'Pavel Raiskup', 'theger']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue34374'
versions = ['Python 3.7']

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.