[Python-Dev] Tracker status

R. David Murray rdmurray at bitdance.com
Tue Aug 3 18:58:31 CEST 2010


On Tue, 03 Aug 2010 16:35:01 +0200, Antoine Pitrou <solipsis at pitrou.net> wrote:
> Apparently you are not the only one experiencing it.
> On #python-dev we get such notifications:
> 
> <CIA-31> alanwilter roundup * #9485/signal.signal/signal.alarm not
> working as expected: [new] I have this example code to illustrate a
> problem I am ...
> <CIA-31> alanwilter roundup * #9486/signal.signal/signal.alarm not
> working as expected: [new] I have this example code to illustrate a
> problem I am ... <fdrake> gutworth: Too late.  tarek is lost to us.
> <CIA-31> alanwilter roundup * #9487/signal.signal/signal.alarm not
> working as expected: [new] I have this example code to illustrate a
> problem I am ...
> <CIA-31> alanwilter roundup * #9488/signal.signal/signal.alarm not
> working as expected: [new] I have this example code to illustrate a
> problem I am ...
> 
> But the relevant bug entries don't exist.

Fixed.  Apparently a line was dropped when applying a patch to
the tracker, but the mistake didn't surface until roundup
was restarted after the reboot.

--
R. David Murray                                      www.bitdance.com


More information about the Python-Dev mailing list