Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2002-July/026529.html below:

[Python-Dev] threads, SIGINT and time.sleep()

• Previous message: [Python-Dev] threads, SIGINT and time.sleep()
• Next message: [Python-Dev] Python version of PySlice_GetIndicesEx
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Python has always documented that signals go only to the main thread.
Apparently in 2.1 and before this wasn't implemented properly (for
Linux; I don't know about other platforms and this is notoriously
platform-dependent).

I think that since ^C doesn't interrupt regular Python code running in
a thread, it's strange that time.sleep() (and presumably other I/O!)
would be interrupted.

So I'd like to see the CVS behavior.

--Guido van Rossum (home page: http://www.python.org/~guido/)

• Previous message: [Python-Dev] threads, SIGINT and time.sleep()
• Next message: [Python-Dev] Python version of PySlice_GetIndicesEx
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4