RetroSearch Browse

Wed Jan 24 19:54:52 CET 2007 · https://mail.python.org/pipermail/python-dev/2007-January/070779.html

On 1/24/07, "Martin v. Löwis" <martin at v.loewis.de> wrote:
>
> Ulisses Furquim schrieb:
> > I've read some threads about signals in the archives and I was under
> > the impression signals should work reliably on single-threaded
> > applications. Am I right?  I've thought about a way to fix this, but I
> > don't know what is the current plan for signals support in python, so
> > what can be done?
>
> I agree it's a bug, and I agree with your proposed analysis. Please
> try to come up with a patch (e.g. by putting a while(is_tripped) loop
> around the for loop). Also make sure you include test case.

   What about http://www.python.org/sf/1564547 ?  It tries to solve a
different problem, but I think it also fixes this one; at least as much as
possible with the braindead unix signal programming interface...

-- 
Gustavo J. A. M. Carneiro
"The universe is always one step beyond logic."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/python-dev/attachments/20070124/bb26a3da/attachment-0001.html 

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2007-January/070779.html below:

[Python-Dev] Problem with signals in a single threaded application