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

Showing content from http://mail.python.org/pipermail/python-dev/2003-June/036276.html below:

[Python-Dev] Where to put the interrupt module?

• Previous message: [Python-Dev] Where to put the interrupt module?
• Next message: [Python-Dev] Where to put the interrupt module?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> > IDLEfork, now in Lib/idlelib, uses a new C extension, the 'interrupt'
> > module.  This is a truly minimal, and generally useful, module to
> > provide a way to cause a KeyboardInterrupt in the main thread from a
> > secondary thread.  I propose to move this to Modules, and make it a
> > toplevel module.  This is the easiest thing in order to get it
> > compiled and built for various platforms.
> 
> +1 on the functionality. But: if it's so small why not simply put it in 
> sys?

Hm, that's not bad.  It should be called sys.interrupt_main() then.

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

• Previous message: [Python-Dev] Where to put the interrupt module?
• Next message: [Python-Dev] Where to put the interrupt module?
• 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