bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Collin Funk <collin.funk1@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>, Gnulib bugs <bug-gnulib@gnu.org>
Subject: Re: gnulib-tool Python tracebacks after control-C
Date: Mon, 13 May 2024 13:48:10 -0700	[thread overview]
Message-ID: <9d1fba37-72eb-4d9e-ac28-68b67dffba35@gmail.com> (raw)
In-Reply-To: <382d9f53-2e34-46a0-9cfb-03081afb1b54@cs.ucla.edu>

Hi Paul,

On 5/13/24 9:39 AM, Paul Eggert wrote:
> I realized that I invoked ' ./gnulib-tool --create-testdir --dir foo stdbit' with the wrong options so I interrupted it with control-C. It then gave me the following long traceback, which is not useful. I suggest shutting off the Python traceback info after control-C unless perhaps some new debugging option is used.

Thanks for the suggestion. I agree, but I need to find the correct way
to do that. IIRC some Python packages I have used do it properly but
others just do an ugly traceback.

I think that control-C raises a KeyboardInterrupt. The Python
documentation notes some special considerations that need to be made
there [1].

Collin

[1] https://docs.python.org/3/library/exceptions.html#KeyboardInterrupt


  reply	other threads:[~2024-05-13 21:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-13 16:39 gnulib-tool Python tracebacks after control-C Paul Eggert
2024-05-13 20:48 ` Collin Funk [this message]
2024-05-13 21:32   ` Pádraig Brady
2024-05-16  3:29     ` Collin Funk
     [not found] ` <24869432.kmuVQn2iE0@nimes>
     [not found]   ` <8121fac5-d072-40fe-b285-4c5777d7203c@gmail.com>
     [not found]     ` <3191653.D8ZAKjAxdT@nimes>
2024-05-17  1:38       ` Collin Funk

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

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9d1fba37-72eb-4d9e-ac28-68b67dffba35@gmail.com \
    --to=collin.funk1@gmail.com \
    --cc=bug-gnulib@gnu.org \
    --cc=eggert@cs.ucla.edu \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).