Add function similar to shutil.move that does not overwrite

Open
#56,950 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
32/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python

Research direction

Start by reading the existing shutil.move implementation and documentation to understand its file and directory handling. Define the non-overwrite behavior and API scope, then add tests covering the relevant move cases; the issue is done when the new function preserves existing destinations and its behavior is documented.

Written by the indexing model from the issue text.

Description

3.7 (EOL) stdlib type-feature
BPO 12741
Nosy @merwok, @stevendaprano

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 2011-08-12.12:41:05.058>
labels = ['3.7', 'type-feature', 'library']
title = 'Add function similar to shutil.move that does not overwrite'
updated_at = <Date 2017-02-08.09:49:57.324>
user = 'https://bugs.python.org/DavidTownshend'

bugs.python.org fields:

activity = <Date 2017-02-08.09:49:57.324>
actor = 'steven.daprano'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2011-08-12.12:41:05.058>
creator = 'David.Townshend'
dependencies = []
files = []
hgrepos = []
issue_num = 12741
keywords = []
message_count = 3.0
messages = ['141952', '141976', '142052']
nosy_count = 3.0
nosy_names = ['eric.araujo', 'steven.daprano', 'David.Townshend']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue12741'
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.