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 eric.smith
Recipients Vojtěch Pachol, docs@python, eric.smith
Date 2016-03-02.11:26:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1456917997.4.0.103754023377.issue26468@psf.upfronthosting.co.za>
In-reply-to
Content
I agree that copy2 should not fail because chmod fails. Could you please provide the entire traceback message when it fails (on both 2.7 and 3.4 or 3.5)? And what OS are you running on, and what filesystem?

It looks like the error happens because errno=95 (EOPNOTSUPP, probably) isn't in the list of errors that _copyxattr catches, while (ENOTSUP=134 on Linux) is.

I think the documentation is also incorrect. Of course copy2 can fail: what about out of disk space? I think the documentation is trying to say that copy2 never fails because it can't preserve metadata. And the wording in the docs "copy2() never returns failure" is also odd, it should say "copy2() never raises an exception because it cannot preserve file metadata".
History
Date User Action Args
2016-03-02 11:26:37eric.smithsetrecipients: + eric.smith, docs@python, Vojtěch Pachol
2016-03-02 11:26:37eric.smithsetmessageid: <1456917997.4.0.103754023377.issue26468@psf.upfronthosting.co.za>
2016-03-02 11:26:37eric.smithlinkissue26468 messages
2016-03-02 11:26:37eric.smithcreate