bpo-26826: Expose copy_file_range in the os module by pablogsal · Pull Request #7255 · python/cpython (original) (raw)

Overall this looks good to me, especially for beta1.

From past experience, an issue that might come up in the future: A build could be done on a system where copy_file_range is defined as far as configure is concerned, yet isn't actually available or supported on the system the binary gets run on (old kernel, etc). This usually results in an EINVAL OSError. not a problem for us, but sometimes our buildbots are weird. So don't be surprised if we need to go adjust conditions under which the tests run vs get skipped in the future.