Josiah Carlson <[EMAIL PROTECTED]> writes:
> There is already a way of making Python source execution atomic with
> respect to other Python code [1].
It's not realistic to expect sys.setcheckinterval be implementable on
other runtimes.
Also, it doesn't provide a way to unblock asynchronous exceptions until
a particular blocking operation completes.
> If you don't want random exceptions being raised in your threads, then
> don't use this method that is capable of raising exceptions somewhat
> randomly.
It's like saying "if you don't want integer addition overflow, then
don't do addition".
I do want asynchronous exceptions, but not anywhere, only in selected
regions (or excluding selected regions). This can be designed well.
--
__("< Marcin Kowalczyk
\__/ [EMAIL PROTECTED]
^^ http://qrnik.knm.org.pl/~qrczak/
_______________________________________________
Python-3000 mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
