This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: Sigpipe handling issue should be documented
Type: behavior Stage: resolved
Components: Documentation Versions: Python 3.8, Python 3.7
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: docs@python Nosy List: Mariatta, docs@python, splbio
Priority: normal Keywords: patch

Created on 2018-05-16 23:55 by splbio, last changed 2022-04-11 14:59 by admin. This issue is now closed.

Pull Requests
URL Status Linked Edit
PR 6773 merged splbio, 2018-05-16 23:55
PR 8798 merged miss-islington, 2018-08-25 02:28
Messages (3)
msg316877 - (view) Author: Alfred Perlstein (splbio) * Date: 2018-05-16 23:55
A common anti-pattern in python used to get rid of "ugly" brokenpipe messages is to set the SIGPIPE handler to SIG_DFL, this however will cause your program to seemingly randomly exit if it makes any socket connections during its lifetime.  (see github PR for more info)
msg324033 - (view) Author: Mariatta (Mariatta) * (Python committer) Date: 2018-08-25 02:29
New changeset 7b0ed43af55c1e2844aa0ccd5e088b2ddd38dbdb by Mariatta (Miss Islington (bot)) in branch '3.7':
bpo-33550: Warn not to set SIGPIPE to SIG_DFL (GH-6773)
msg324034 - (view) Author: Mariatta (Mariatta) * (Python committer) Date: 2018-08-25 02:32
Date User Action Args
2022-04-11 14:59:00adminsetgithub: 77731
2018-08-25 02:32:02Mariattasetstatus: open -> closed
versions: - Python 2.7, Python 3.4, Python 3.5, Python 3.6
messages: + msg324034

resolution: fixed
stage: patch review -> resolved
2018-08-25 02:29:01Mariattasetnosy: + Mariatta
messages: + msg324033
2018-08-25 02:28:17miss-islingtonsetkeywords: + patch
stage: patch review
pull_requests: + pull_request8389
2018-05-16 23:55:52splbiocreate