Re: [Python-Dev] stuck issue 26826

2016-08-04 Thread Nick Coghlan
On 4 August 2016 at 06:32, Marcos Dione wrote: > Maybe you're right. Maybe, to keep Python's own code simple, we could > skip these optimizations, and leave them in a 3rd party module. Having the scandir package on PyPI made it possible for folks to quantify the

Re: [Python-Dev] stuck issue 26826

2016-08-03 Thread Martin Panter
On 03/08/2016, Marcos Dione wrote: > Hi pythonistas. A couple of moths ago I opened an issue in the bug > tracker for adding a new syscall to the os module. It's based on new > developments in the Linux kernel. Here's the link: > > https://bugs.python.org/issue26826 To

Re: [Python-Dev] stuck issue 26826

2016-08-03 Thread Random832
On Wed, Aug 3, 2016, at 16:32, Marcos Dione wrote: > (it needs to check the availability of the function and the suitability > for the parameters given; copy_file_range() only works on files on the > same filesystem[1]). Hmm... What is the benefit to using copy_file_range over sendfile in this

Re: [Python-Dev] stuck issue 26826

2016-08-03 Thread Terry Reedy
On 8/3/2016 1:23 PM, Marcos Dione wrote: Hi pythonistas. A couple of moths ago I opened an issue in the bug tracker for adding a new syscall to the os module. It's based on new developments in the Linux kernel. Here's the link: https://bugs.python.org/issue26826 I suggest that at some

Re: [Python-Dev] stuck issue 26826

2016-08-03 Thread Marcos Dione
On Wed, Aug 03, 2016 at 11:31:46AM -0700, Guido van Rossum wrote: > Then again are people really concerned about the speed of those file > copy functions? Or are we just offering a solution in search of a > problem? At kernel level: clearly yes, otherwise their BDFL would noy allow those[1]

Re: [Python-Dev] stuck issue 26826

2016-08-03 Thread Marcos Dione
On Wed, Aug 03, 2016 at 10:46:13AM -0700, Guido van Rossum wrote: > I wonder if the issue isn't that there are so many Linux syscalls that > we probably should have a process for deciding which ones are worth > supporting in the os module, and that process should not necessarily > start with a

Re: [Python-Dev] stuck issue 26826

2016-08-03 Thread Guido van Rossum
I wonder if the issue isn't that there are so many Linux syscalls that we probably should have a process for deciding which ones are worth supporting in the os module, and that process should not necessarily start with a patch review. What fraction of Linux syscalls do we currently support? What

[Python-Dev] stuck issue 26826

2016-08-03 Thread Marcos Dione
Hi pythonistas. A couple of moths ago I opened an issue in the bug tracker for adding a new syscall to the os module. It's based on new developments in the Linux kernel. Here's the link: https://bugs.python.org/issue26826 After two months and a half I managed to create a nice patch with