[Python-ideas] Implementation of shutil.move

David Townshend aquavitae69 at gmail.com
Sun Aug 14 16:09:32 CEST 2011

It seems there's a second problem too - move on remote file systems use copy
rather than rename, so changing the implementation means changing it for
copy too, which is more difficult. Maybe the best option is to try to apply
some sort of locking mechanism, but I can't see how right now.
On Aug 14, 2011 4:01 PM, "Christian Heimes" <lists at cheimes.de> wrote:
> Am 14.08.2011 08:01, schrieb David Townshend:
>> The latest idea (which I've now described on the issue tracker), is not
>> use os.open(), rather os.link() and os.unlink(), which should work the
>> across platforms. Please could someone correct me if I'm wrong about
> My proposed link() / unlink() procedure works only on platforms and file
> systems, that support hard links. I totally forgot about the file system
> issue, sorry. :)
> Hard links won't work on a FAT32 mount point on Unix and probably not on
> Samba shares, too. It might work on NTFS if the VFS implements it but
> NTFS has a limited reference counter for hard links. It might be
> possible that a rename() op would work but a link() op wouldn't.
> Christian
> _______________________________________________
> Python-ideas mailing list
> Python-ideas at python.org
> http://mail.python.org/mailman/listinfo/python-ideas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-ideas/attachments/20110814/f242b356/attachment.html>

More information about the Python-ideas mailing list