➜

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 giampaolo.rodola
Recipients eryksun, giampaolo.rodola, greggman, ned.deily, paul.moore, ronaldoussoren, steve.dower, tim.golden, zach.ware
Date 2019-11-27.10:57:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <[email protected]>
In-reply-to
Content
If we use CopyFileExW in copy2(), then also copystat() and copymode() should be able to copy the same metadata/security-bits/etc as CopyFileExW. I don't know which Windows APIs should be used though.

I sort of agree with Steven that CopyFileExW could be used everywhere (meaning copyfile()), but that basically means breaking backward compatibility re. what is promised in the doc, and am not sure how to deal with that. For that reason it's probably it's better to leave copyfile() alone. 

On macOS it seems we can use fcopyfile(3) syscall (which is already exposed) and its flag argument (COPYFILE_METADATA, COPYFILE_DATA. COPYFILE_XATTR, etc,) to implement both copy2() and copystat() / copymode().
History
Date User Action Args
2019-11-27 10:57:27giampaolo.rodolasetrecipients: + giampaolo.rodola, paul.moore, ronaldoussoren, tim.golden, ned.deily, zach.ware, eryksun, steve.dower, greggman
2019-11-27 10:57:27giampaolo.rodolasetmessageid: <[email protected]>
2019-11-27 10:57:27giampaolo.rodolalinkissue38906 messages
2019-11-27 10:57:26giampaolo.rodolacreate