"Marcin 'Qrczak' Kowalczyk" <[EMAIL PROTECTED]> wrote:
> "tomer filiba" <[EMAIL PROTECTED]> writes:
>
> > once a thread is created, there is no way to kill it *externally*.
> > which is a pity, since the thread must be "willing" to die,
>
> Doing that unconditionally is impractical: the thread h
"tomer filiba" <[EMAIL PROTECTED]> writes:
> once a thread is created, there is no way to kill it *externally*.
> which is a pity, since the thread must be "willing" to die,
Doing that unconditionally is impractical: the thread has no way
to protect itself from being killed at moments it has inva
"tomer filiba" <[EMAIL PROTECTED]> wrote:
>
> > I'm curious as to what I have done to deserve the rudeness of your reply.
> well, i'm kinda pissed off by rockets flying over my house, svn giving me a
> hard life, and what not. but what you have done was dismissing my post on
> shaky grounds.
Ick
> I'm curious as to what I have done to deserve the rudeness of your reply.
well, i'm kinda pissed off by rockets flying over my house, svn giving me a
hard life, and what not. but what you have done was dismissing my post on
shaky grounds.
if all you meant was adding this support for the 2.x bran
"tomer filiba" <[EMAIL PROTECTED]> wrote:
>
> > [...] it could be implemented as a debugging trace function
>
> even if it could be, *why*? you can't really suggest that from now on,
> every multithreaded app must run in trace mode, right? it's a performance
> penalty for no good reason -- it's
> [...] it could be implemented as a debugging trace function
even if it could be, *why*? you can't really suggest that from now on,
every multithreaded app must run in trace mode, right? it's a performance
penalty for no good reason -- it's a question of API.
just as the API lets you *create* th
"tomer filiba" <[EMAIL PROTECTED]> wrote:
> python's threading model seems too weak imo. i'm not talking about
> the GIL and the fact threads run one at a time -- i'm talking about the
> incompleteness of the API of thread module.
I could have sworn that it could be implemented as a debugging tra
python's threading model seems too weak imo. i'm not talking about
the GIL and the fact threads run one at a time -- i'm talking about the
incompleteness of the API of thread module.
once a thread is created, there is no way to kill it *externally*. which
is a pity, since the thread must be "willi
Greg Ewing wrote:
> Ron Adam wrote:
>
>> I'm still not sure why "__round__" should be preferred in place of
>> "round" as a method name. There isn't an operator associated to
>> rounding so wouldn't the method name not have underscores?
>
> I was thinking there would be functions such as round
Ron Adam wrote:
> I'm still not sure why "__round__" should be preferred in place of
> "round" as a method name. There isn't an operator associated to
> rounding so wouldn't the method name not have underscores?
I was thinking there would be functions such as round(),
trunc(), etc. that use __
10 matches
Mail list logo
