Shutil Move Creates an Extra Directory Level: Inspect the Destination First
By ON Lab · Sources checked November 9, 2026
An existing directory destination means “move inside.” A missing destination can become the moved directory’s new name. Test the final tree in a temporary directory before touching real files.
Reproduce the boundary in a disposable example
Moving a directory nests it inside an existing destination instead of renaming it.
from pathlib import Path
from tempfile import TemporaryDirectory
import shutil
with TemporaryDirectory() as temporary:
root = Path(temporary)
source = root / "incoming"
source.mkdir()
(source / "note.txt").write_text("sample")
existing = root / "archive"
existing.mkdir()
returned = Path(shutil.move(str(source), str(existing)))
assert returned == existing / "incoming"
assert (existing / "incoming" / "note.txt").read_text() == "sample"
source2 = root / "another"
source2.mkdir()
(source2 / "note.txt").write_text("second")
renamed = root / "renamed"
shutil.move(str(source2), str(renamed))
assert (renamed / "note.txt").read_text() == "second"
print("existing versus missing destination verified")Read the result before changing application code
The assertions check actual file placement and contents, not merely the function returning without error. Print or inspect the planned source and destination before a real move. Also inspect symlinks: a path that leads to a directory can behave as a directory destination even when its spelling looks like a new filename.
Choose the behavior your caller needs
If the task is renaming a directory, choose a destination that satisfies that contract and handle collisions explicitly. If the task is merging contents, define conflict behavior separately; moving a directory onto a directory is not a general merge specification. Keep a backup for important data and verify the resulting tree before deleting any independent backup. Cross-filesystem moves may involve copying and removing rather than an atomic rename.
Scope and limits
Only disposable local files are moved here. The example does not establish metadata preservation, atomicity, or safe replacement of a destination changed concurrently.
Related: compare the adjacent data or execution boundary.
The embedded example was executed in an isolated local Python process on November 9, 2026. It is a reproducible boundary check, not a test of your full application.