➜

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 eryksun
Recipients eryksun, paul.moore, stephan, steve.dower, tim.golden, vstinner, zach.ware
Date 2016-10-04.15:26:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1475594795.23.0.632168801619.issue28356@psf.upfronthosting.co.za>
In-reply-to
Content 
In scanning over issue 8828, I see no discussion of the consequences of not using MOVEFILE_COPY_ALLOWED in Antoine's patch, so it appears that this behavior change was unintentional.

> For now I switched to shutil.move() but I suppose its not
> as performant/optimal as an "move" or "rename" directly 
> supported by the OS.

Correct, the copy employed by shutil.move for a cross-volume move is not as optimized as what MoveFile uses (basically CopyFile), but unless you're moving a file that's very large it shouldn't matter, and even then without testing I don't know if it's a significant difference relative to the throughput of the disk(s) involved.
History
Date User Action Args
2016-10-04 15:26:35eryksunsetrecipients: + eryksun, paul.moore, vstinner, tim.golden, zach.ware, steve.dower, stephan
2016-10-04 15:26:35eryksunsetmessageid: <1475594795.23.0.632168801619.issue28356@psf.upfronthosting.co.za>
2016-10-04 15:26:35eryksunlinkissue28356 messages
2016-10-04 15:26:35eryksuncreate