From: <Paul_Koning@Dell.com>
To: <kevin.pouget@gmail.com>, <khooyp@cs.umd.edu>
Cc: <tromey@redhat.com>, <gdb-patches@sourceware.org>, <dje@google.com>
Subject: RE: Handle SIGINT in Python
Date: Fri, 13 Jan 2012 12:11:00 -0000 [thread overview]
Message-ID: <09787EF419216C41A903FD14EE5506DD030FCF112D@AUSX7MCPC103.AMER.DELL.COM> (raw)
In-Reply-To: <CAPftXUKSb6ndq0jXLgFpSgUU5Tgiq0FLbR=nMnuhv610K8dcMA@mail.gmail.com>
>...
>> 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 ...
But it is in every Python program; if you program in Python it's part of what you do. Python, unlike many other programming languages, treats exceptions 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
next prev parent reply other threads:[~2012-01-13 11:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 21:31 Khoo Yit Phang
2012-01-10 21:47 ` Doug Evans
2012-01-10 22:09 ` Khoo Yit Phang
2012-01-11 20:59 ` Tom Tromey
2012-01-11 21:06 ` Paul_Koning
2012-01-11 21:23 ` Tom Tromey
2012-01-12 0:54 ` Doug Evans
2012-01-12 15:52 ` Kevin Pouget
2012-01-12 16:48 ` Paul_Koning
2012-01-13 10:55 ` Kevin Pouget
2012-01-13 12:11 ` Paul_Koning [this message]
2012-01-10 21:49 ` Tom Tromey
2012-01-11 21:15 ` Tom Tromey
2012-01-11 21:49 ` Khoo Yit Phang
2012-01-11 22:46 ` Khoo Yit Phang
2012-01-20 21:40 ` Tom Tromey
2012-01-22 16:36 ` Khoo Yit Phang
2012-01-22 20:54 ` Khoo Yit Phang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=09787EF419216C41A903FD14EE5506DD030FCF112D@AUSX7MCPC103.AMER.DELL.COM \
--to=paul_koning@dell.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=kevin.pouget@gmail.com \
--cc=khooyp@cs.umd.edu \
--cc=tromey@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox