[Python-Dev] Tracker status (original) (raw)

Brian Curtin brian.curtin at gmail.com
Tue Aug 3 19:05:57 CEST 2010

On Tue, Aug 3, 2010 at 11:58, R. David Murray <rdmurray at bitdance.com> wrote:

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: > > alanwilter roundup * #9485/signal.signal/signal.alarm not > working as expected: [new] I have this example code to illustrate a > problem I am ... > alanwilter roundup * #9486/signal.signal/signal.alarm not > working as expected: [new] I have this example code to illustrate a > problem I am ... gutworth: Too late. tarek is lost to us. > alanwilter roundup * #9487/signal.signal/signal.alarm not > working as expected: [new] I have this example code to illustrate a > problem I am ... > 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

Are these issues going to show up or are they lost? Via IRC, #9490 and it's apparent dupe #9491 looked interesting to me (Windows service related). -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20100803/e1598062/attachment.html>

More information about the Python-Dev mailing list