This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients jshholland, paul.moore, pitrou, serhiy.storchaka
Date 2015-05-18.19:07:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1431976070.22.0.780406677166.issue24229@psf.upfronthosting.co.za>
In-reply-to
Content
File renaming is simple and usually atomic operation. File copying is complex operation. What memory buffer should be used for copying? What to do with growing files or reading with errors? Should file space be preallocated before copyiong to decrease fragmentation? How handle sparse files? Can be optimized copyiong on file systems with compression? What to do with NT streams? What to do with extended attributes? What to do with directories, links and other special files?

I think that pathlib is not good place for this function (as well as for handling ZIP files or playing multimedia).
History
Date User Action Args
2015-05-18 19:07:50serhiy.storchakasetrecipients: + serhiy.storchaka, paul.moore, pitrou, jshholland
2015-05-18 19:07:50serhiy.storchakasetmessageid: <1431976070.22.0.780406677166.issue24229@psf.upfronthosting.co.za>
2015-05-18 19:07:50serhiy.storchakalinkissue24229 messages
2015-05-18 19:07:49serhiy.storchakacreate