[Python-3000] python-safethread project status

[Jeffrey Yasskin]

FWIW, I think thread interruption/cancellation deserves a PEP. There
are a bunch of subtle issues like this, several other languages that
we can imitate, and a lot of places in the implementation that will
need to change to support it. I was planning to write the PEP a month
or two from now, but if someone else gets there first, I'll be happy
to help.

On Tue, Mar 18, 2008 at 7:47 PM, Greg Ewing <greg.ewing at canterbury.ac.nz> wrote:
> Adam Olsen wrote:
>  > I'd tend to assume only *purely* functional languages should have
>  > asynchronous interrupts.  Any imperative language with them is
>  > suspect.
>
>  Yet there are situations where *not* having any such thing
>  can be extremely inconvenient.
>
>  If I'm performing some background calculation that only
>  munges on its own data, and doesn't touch anything shared,
>  it's quite safe to kill it at any point and throw away
>  everything it was working on.
>
>  Being unable to do that from outside means that I have
>  to sprinkle explicit tests through it for an abort flag,
>  which is a horrible thing to have to do from a software
>  engineering standpoint for many reasons.
>
>  In the consenting-adults environment of Python, I don't
>  like having a useful facility withheld from me just
>  because it's possible to misuse it.
>
>  --
>  Greg
>
>
> _______________________________________________
>  Python-3000 mailing list
>  Python-3000 at python.org
>  http://mail.python.org/mailman/listinfo/python-3000
>  Unsubscribe: http://mail.python.org/mailman/options/python-3000/jyasskin%40gmail.com
>



-- 
Namasté,
Jeffrey Yasskin
http://jeffrey.yasskin.info/