Re: Killing threads, and os.system()

2012-02-03 Thread Paul Rubin
John Nagle writes: > QNX's message passing looks more like a subroutine call than an > I/O operation, How do they enforce process isolation, or do they decide they don't need to? -- http://mail.python.org/mailman/listinfo/python-list

Re: Killing threads, and os.system()

2012-02-03 Thread Steven D'Aprano
On Fri, 03 Feb 2012 00:14:33 -0800, John Nagle wrote: > I won't even get into the appalling mess around the Global Interpreter > Lock. You know full well that IronPython and Jython don't have a GIL. If the GIL was as harmful as you repeatedly tell us, why haven't you, and everyone else, migrate

Re: Killing threads, and os.system()

2012-02-03 Thread John Nagle
On 1/31/2012 8:04 AM, Dennis Lee Bieber wrote: ({muse: who do we have to kill to persuade OS designers to incorporate something like the Amiga ARexx "rexxport" system}). QNX, which is a real-time microkernel which looks like POSIX to applications. actually got interprocess communication rig

Re: Killing threads, and os.system()

2012-01-31 Thread Laurent Claessens
Le 31/01/2012 17:04, Dennis Lee Bieber a écrit : Of course, if that thread is stuck waiting for a call to os.system() to complete, then it can not do anything... os.system() is a rather limited, restrictive, call -- best used for quick one-of operations. If running Python 2.