Bugs item #1326841, was opened at 2005-10-14 14:48 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1326841&group_id=5470
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Demos and Tools Group: None Status: Open Resolution: None Priority: 5 Submitted By: paul rubin (phr) Assigned to: Nobody/Anonymous (nobody) Summary: SIGALRM alarm signal kills interpreter Initial Comment: This may be similar to #210641. Example (Python 2.4.1, Fedora Core 4 GNU/Linux): sh-3.00$ python Python 2.4.1 (#1, May 16 2005, 15:19:29) [GCC 4.0.0 20050512 (Red Hat 4.0.0-5)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import signal >>> signal.alarm(1) # 1 second passes... 0 >>> Alarm clock sh-3.00$ # python has exited Doing the same thing in IDLE results in the subprocess restarting. IMO the correct behavior would be to raise an exception that the outer shell would catch. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1326841&group_id=5470 _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
