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

Showing content from https://mail.python.org/pipermail/python-dev/2012-April/118917.html below:

Protecting cleanup statements from interruptions

• Previous message: [Python-Dev] PEP-419: Protecting cleanup statements from interruptions
• Next message: [Python-Dev] Removing surplus fields from the frame object and not adding any new ones.
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> PEP: 419
> Title: Protecting cleanup statements from interruptions
> Version: $Revision$
> Last-Modified: $Date$
> Author: Paul Colomiets <paul at colomiets.name>
> Status: Draft
> Type: Standards Track
> Content-Type: text/x-rst
> Created: 06-Apr-2012
> Python-Version: 3.3

Hi, I think your PEP should at least mention that the
signal.pthread_sigmask() exists, function added to Python 3.3.

signal.pthread_sigmask() is maybe less practical than your proposition
(each finally block has to be patched), but it is the best way to
ignore temporary signals. Using signal.pthread_sigmask(), you
guarantee that EINTR will not occurs... if you use it on all threads!

http://mail.python.org/pipermail/python-ideas/2012-April/014749.html

Victor

• Previous message: [Python-Dev] PEP-419: Protecting cleanup statements from interruptions
• Next message: [Python-Dev] Removing surplus fields from the frame object and not adding any new ones.
• 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