I still do not like "non-class class" because this is a contradiction
in itself.
Anyway a non-class class is a class whose objects may not get a
method attached. So far so good, but that was obvious.
Am Dienstag, 2. September 2014, 16:29:41 schrieb Glyph Lefkowitz:
> Except I think it might be
On Sep 1, 2014, at 3:24 PM, Wolfgang Rohdewald
wrote:
> What is a non-class class or rather what sort of types is meant to
> be insecure?
Jelly is dynamically typed, so any value might show up in any position. In
this case, a value shows up in the slot in the serialization of a method object
On 01:38 pm, j...@editshare.com wrote:
FWIW, looking at your original code, you may also want to call your
Deferreds in a reactor.callLater. I learned the hard way that if you
callback a Deferred from processEnded and the callback spawns another
process, your process will still be Twisted's
On 09/02/2014 09:31 AM, Adi Roiban wrote:
Problem solved... see below
On 2 September 2014 12:05, Justin Mazzola Paluska wrote:
On 09/02/2014 05:08 AM, Adi Roiban wrote:
[snip]
if pid:
self.processEnded(status)
unregisterReapProcessHandler(pid, self)
Problem solved... see below
On 2 September 2014 12:05, Justin Mazzola Paluska wrote:
> On 09/02/2014 05:08 AM, Adi Roiban wrote:
[snip]
> if pid:
> self.processEnded(status)
> unregisterReapProcessHandler(pid, self)
> elif pid == 0:
> # Twisted
On Sep 2, 2014 8:22 AM, "Akira Li" <4kir4...@gmail.com> wrote:
>
> Justin Mazzola Paluska writes:
>
> Unrelated.
>
> > def unstick():
> > reapAllProcesses()
> > reactor.callLater(1, unstick)
> >
>
> Why do you use `unstick` instead of `reapAllProcesses` dire
Justin Mazzola Paluska writes:
Unrelated.
> def unstick():
> reapAllProcesses()
> reactor.callLater(1, unstick)
>
Why do you use `unstick` instead of `reapAllProcesses` directly.
Do you expect that `reapAllProcesses` name will be rebound in the future?
On 09/02/2014 05:08 AM, Adi Roiban wrote:
Hi,
While using spawnProcess on Linux I found out that when an invalid
executable is called there is a corner case in which a zombie process
is left until main process exists and can not be closed.
I wrote a test for this but I was not able to reproduce
Hi,
While using spawnProcess on Linux I found out that when an invalid
executable is called there is a corner case in which a zombie process
is left until main process exists and can not be closed.
I wrote a test for this but I was not able to reproduce this error in
isolation, event if I run the
