[Python-Dev] Inherance of file descriptor and handles on Windows (PEP 446) (original) (raw)
Guido van Rossum guido at python.org
Thu Jul 25 02:41:22 CEST 2013
- Previous message: [Python-Dev] Inherance of file descriptor and handles on Windows (PEP 446)
- Next message: [Python-Dev] Inherance of file descriptor and handles on Windows (PEP 446)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, Jul 24, 2013 at 3:35 PM, Antoine Pitrou <solipsis at pitrou.net> wrote:
On Wed, 24 Jul 2013 15:25:50 -0700 Guido van Rossum <guido at python.org> wrote:
>> To reduce the need for 3rd party subprocess creation code, we should >> have better daemon creation code in the stdlib -- I wrote some damn >> robust code for this purpose in my previous job, but it never saw the >> light of day. > > What do you call "daemon"? An actual Unix-like daemon?
Yeah, a background process with parent PID 1 and not associated with any terminal group. But is that relevant to the PEP? A daemon only uses fork(), not exec(). Or have I misunderstood your concern?
Actually it's common for "daemonization" libraries to run an arbitrary executable as a daemon, and then it would be relevant. E.g. zdaemon (https://pypi.python.org/pypi/zdaemon) does this. (Disclosure: I wrote the first version of zdaemon when I worked for Zope Corp over a decade ago. :-)
-- --Guido van Rossum (python.org/~guido)
- Previous message: [Python-Dev] Inherance of file descriptor and handles on Windows (PEP 446)
- Next message: [Python-Dev] Inherance of file descriptor and handles on Windows (PEP 446)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]