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 | StyXman, desbma, facundobatista, giampaolo.rodola, martin.panter, ncoghlan, neologix, petr.viktorin, vstinner |
| Date | 2019年03月11日.20:06:35 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1552334795.76.0.587847099009.issue26826@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
Little update about this. According to: http://man7.org/linux/man-pages/man2/copy_file_range.2.html ...it seems glibc 2.27 released on 2018年02月01日 includes copy_file_range(). I'm not the best candidate for giving advice on C syscalls definitions/availability, but FWIW this works on my Linux 4.15: #if defined(__linux__) && \ defined(SYS_copy_file_range) && \ defined(__GLIBC_PREREQ) && \ __GLIBC_PREREQ(2, 27) ... #endif I think (but not sure) this is supposed to fix this condition, which appears to be the major blocker here: https://github.com/python/cpython/blob/9a177061cd7190eabf40efd31e8981e0bccd5dc4/Lib/test/test_os.py#L258-L261 |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019年03月11日 20:06:35 | giampaolo.rodola | set | recipients: + giampaolo.rodola, facundobatista, ncoghlan, vstinner, StyXman, petr.viktorin, neologix, martin.panter, desbma |
| 2019年03月11日 20:06:35 | giampaolo.rodola | set | messageid: <1552334795.76.0.587847099009.issue26826@roundup.psfhosted.org> |
| 2019年03月11日 20:06:35 | giampaolo.rodola | link | issue26826 messages |
| 2019年03月11日 20:06:35 | giampaolo.rodola | create | |