bpo-26791: update shutil.move() to provide the same symlink move behavior as the mv shell when moving a symlink into a directory that is the target of the symlink#21759
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
shutil.move() calls _samefile() to check whether a destination directory and a source path resolve to the same path. If they do, it assumes (per comment) that it is because of a case-insensitive filesystem and calls os.rename() to perform the move. When the source is a symlink that resolves to the destination directory, os.rename() raises an exception that is returned to the shutil.move() caller. By contrast, the mv shell command moves the symlink into the directory.
A solution to get the mv behavior is to check whether the source is a symlink when _samefile() returns True in order to bypass the os.rename() call and trigger the normal symlink handling in shutil.move().
https://bugs.python.org/issue26791