From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7901 invoked by alias); 13 Jan 2012 11:55:58 -0000 Received: (qmail 7892 invoked by uid 22791); 13 Jan 2012 11:55:57 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from ausc60ps301.us.dell.com (HELO ausc60ps301.us.dell.com) (143.166.148.206) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 13 Jan 2012 11:55:44 +0000 X-Loopcount0: from 10.175.216.250 From: To: , CC: , , Date: Fri, 13 Jan 2012 12:11:00 -0000 Subject: RE: Handle SIGINT in Python Message-ID: <09787EF419216C41A903FD14EE5506DD030FCF112D@AUSX7MCPC103.AMER.DELL.COM> References: <09787EF419216C41A903FD14EE5506DD030F1EB37E@AUSX7MCPC103.AMER.DELL.COM> In-Reply-To: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-01/txt/msg00471.txt.bz2 >... >> Any Python statement can throw a KeyboardException. >That could make sense in a stateless / lightweight application, but in >[my] GDB-base Python application, I can't see how this can remain the >default behavior ...=20 But it is in every Python program; if you program in Python it's part of wh= at you do. Python, unlike many other programming languages, treats excepti= ons as a major mechanism that's ingrained in everything. It's not missing = (as in C) or more of an afterthought (as in C++). I think that having GDB/= Python work differently would make it feel quite unPythonic. paul=20