homepage

shutil.move does not behave as I expect when moving a symlink across filesystems. (This is when src itself is a symlink, not when it is a directory tree including symlinks.)
-If src is a symlink to file, rather than moving the symlink, it copies the contents of the file
-If src is a symlink to a directory, rather than moving the symlink, it copies the contents of the directory to a new directory
-If src is a dangling symlink, it errors out
Attached patch against the py3k branch adds tests for these cases and adds the expected behaviour, which is to recreate the symlink.
(I have encountered this on 2.6 - current SVN; it is probably in 2.5 as well but I have not confirmed.)

I can confirm that the tests fail before the patch (but if an only if /tmp is a different file system from the one where the build is, see issue 9999) and pass after the patch. The patch itself looks good to me and does accord better with how 'mv' works.

I work on the superficially related #12715 (symlinks for shutil). As we try to mimic the POSIX tools and `mv` indeed doesn't follow links, I agree with the approach of this patch.

Can you update the documentation?

Éric, here's a quick docs-only patch against current default...does this do the job?

Thanks for the doc patch, which looks good. I have one question: if a relative symlink is copied, should the resulting symlink be relative too?

Éric: I think copying a relative symlink should also be relative, and that's the behaviour of this patch. That was the use case that tripped me up with the original behaviour of shutil.move: a relative symlink which was dangling in its original location, but not once moved. (This was, believe it or not, intentional design....)
This is also the behaviour when src and dst are on the same filesystem. Basically my intention was to remove the distinction between "same filesystem" and "different filesystem."

Looks good to me.

Antoine, would you mind taking this one?

Ow, I'm sorry for overlooking this. I thought you would take it.
Unfortunately the patch is now broken because of 5b61334bb776.
(technically it applies, but the tests don't run anymore because the "other filesystem" now uses a mocking approach)
By the way, I think this shouldn't be applied to bugfix branches, since it's a behaviour change.

I took the liberty to fix the tests.
Basically I've adapted them to the new mock based cross file system approach (that doesn't depend on luck anymore :)).
I also had to add one more `os.path.realpath` because on some OS (like OS X) the tmp directory path already consists of symlinks.
I didn't touch the actual code.
Tested on OS X and Ubuntu Linux (Oneiric).

Thanks! I think we also need a doc update for the change in behaviour (with a "versionchanged" tag).

Oh sorry, I didn't look into the doc patch.
I unified both into one patch and added the versionchanged tag and also updated the docstring of shutil.move.

New changeset 1ea8b7233fd7 by Antoine Pitrou in branch 'default':
Issue #9993: When the source and destination are on different filesystems,
http://hg.python.org/cpython/rev/1ea8b7233fd7 

Patch now committed to 3.3. Thank you Jonathan and Hynek!