Killing threads during development.

Discussion in 'Python' started by Don Garrett, Jun 5, 2005.

  1. Don Garrett

    Don Garrett Guest

    I've been developing with external multi-threaded libraries recently.
    I find it difficult to use the Python prompt to experiment with these
    libraries because there isn't any way to just shutdown all threads and
    try things again.

    If I try to exit the prompt with background threads running, then
    Python hangs and I have to kill the process to exit. Ctrl C won't do
    it.

    Is there some way to brutally kill all background threads? Just for
    development purposes?

    Note:
    This isn't an insurmountable problem. If I write test scripts and run
    them from the command line I can still kill them easily. I just find it
    frustrating not be to able to explore interactively while working with
    a new library.
     
    Don Garrett, Jun 5, 2005
    #1
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. cppaddict
    Replies:
    20
    Views:
    820
    Chris Uppal
    Aug 11, 2004
  2. Michael Kearns
    Replies:
    35
    Views:
    1,832
  3. Tony Meyer
    Replies:
    8
    Views:
    513
    Robin Becker
    Apr 13, 2005
  4. jimzat

    Killing subservient threads

    jimzat, Feb 20, 2009, in forum: Python
    Replies:
    6
    Views:
    326
  5. Killing threads

    , Apr 5, 2009, in forum: Python
    Replies:
    13
    Views:
    537
Loading...

Share This Page