[Python-3000] threading, part 2 (original) (raw)
Marcin 'Qrczak' Kowalczyk qrczak at knm.org.pl
Fri Aug 11 19:00:07 CEST 2006
- Previous message: [Python-3000] threading, part 2
- Next message: [Python-3000] threading, part 2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Josiah Carlson <jcarlson at uci.edu> 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 _/ qrczak at knm.org.pl ^^ http://qrnik.knm.org.pl/~qrczak/
- Previous message: [Python-3000] threading, part 2
- Next message: [Python-3000] threading, part 2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]