[issue26826] Expose new copy_file_range() syscall in os module.

[Marcos Dione]

Marcos Dione added the comment:

Fixed the last comments, including comparing what was written to the original data, but only to the length of what was actually written. I'm just not sure if the way to handle the syscall not existing is ok.

----------
Added file: http://bugs.python.org/file43318/copy_file_range.diff

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26826>
_______________________________________