On May 19, 11:31 am, "Chris Mellon" <[EMAIL PROTECTED]> wrote:
> On Mon, May 19, 2008 at 11:36 AM, Roger Heathcote
> > Fair point, but for sub processes that need to be in close contact with the
> > original app, or very small functions that you'd like 100s or 1000s of it
> > seems like a kludge ha
On May 19, 8:16 pm, "Gabriel Genellina" <[EMAIL PROTECTED]>
wrote:
> En Mon, 19 May 2008 20:07:06 -0300, Paul Rubin
> <"http://phr.cx"@NOSPAM.invalid> escribió:
>
> > blaine <[EMAIL PROTECTED]> writes:
> >> How is it that you recommend killing a pure python thread?
>
> Make the thread cooperate. It
En Mon, 19 May 2008 20:07:06 -0300, Paul Rubin
<"http://phr.cx"@NOSPAM.invalid> escribió:
blaine <[EMAIL PROTECTED]> writes:
How is it that you recommend killing a pure python thread?
Make the thread cooperate. It should periodically check some variable or
condition, and cleanly exit when
blaine <[EMAIL PROTECTED]> writes:
> How is it that you recommend killing a pure python thread? And also,
> when i use the 'threading' module am I creating a process, or a (gasp)
> thread?
A thread.
> (Is this an obvious question - and if so, how does one create
> a 'process'?)
os.fork()
--
http
How is it that you recommend killing a pure python thread? And also,
when i use the 'threading' module am I creating a process, or a (gasp)
thread? (Is this an obvious question - and if so, how does one create
a 'process'?)
Thanks!
--
http://mail.python.org/mailman/listinfo/python-list
On Mon, May 19, 2008 at 11:36 AM, Roger Heathcote
<[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
>>
>> On May 16, 11:40 am, Roger Heathcote <[EMAIL PROTECTED]>
>> wrote:
>>>
>>> Despite many peoples insistence that allowing for the arbitrary killing
>>> of threads is a cardinal sin and altho
[EMAIL PROTECTED] wrote:
On May 16, 11:40 am, Roger Heathcote <[EMAIL PROTECTED]>
wrote:
Despite many peoples insistence that allowing for the arbitrary killing
of threads is a cardinal sin and although I have no particular threading
problem to crack right now I remain interest in the taboo that
On May 16, 11:40 am, Roger Heathcote <[EMAIL PROTECTED]>
wrote:
> Hello everyone, this is my first post so hello & please be gentle!
>
> Despite many peoples insistence that allowing for the arbitrary killing
> of threads is a cardinal sin and although I have no particular threading
> problem to cr
I'm not sure it's possible to kill a thread in Python that's in the middle
of a C function. I know you can't do it with signals, for example. Or can
you? I'm on Windows and signals isn't fully implemented.
I had to do just this, btw, so I wrote another Python program that
communicates with the
I'm not sure it's possible to kill a thread in Python that's in the middle
of a C function. I know you can't do it with signals, for example. Or can
you? I'm on Windows and signals isn't fully implemented.
I had to do just this, btw, so I wrote another Python program that
communicates with t
Hello everyone, this is my first post so hello & please be gentle!
Despite many peoples insistence that allowing for the arbitrary killing
of threads is a cardinal sin and although I have no particular threading
problem to crack right now I remain interest in the taboo that is thread
killing.
11 matches
Mail list logo
