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 fraction of BSD syscalls? How much of this is better served by a 3rd party module? Certainly it's not rocket science to write a C extension module that wraps a syscall or a bunch of them.
On Wed, Aug 3, 2016 at 10:23 AM, Marcos Dione <mdi...@grulic.org.ar> 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 > > After two months and a half I managed to create a nice patch with > unit tests and documentation (yay!), but then the issue went cold. I > would like to know how to proceed to get the issue going again. > > Cheers, > > -- Marcos. > > -- > (Not so) Random fortune: > Terrorism isn't a crime against people or property. It's a crime against > our minds, using the death of innocents and destruction of property to > make us fearful. > -- Bruce Schneier > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/guido%40python.org -- --Guido van Rossum (python.org/~guido) _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
