[issue33550] Sigpipe handling issue should be documented

2018-08-24 Thread Mariatta Wijaya
Mariatta Wijaya added the comment: Thanks! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: -Python 2.7, Python 3.4, Python 3.5, Python 3.6 ___ Python tracker

[issue33550] Sigpipe handling issue should be documented

2018-08-24 Thread miss-islington
Change by miss-islington : -- keywords: +patch pull_requests: +8389 stage: -> patch review ___ Python tracker ___ ___

[issue33550] Sigpipe handling issue should be documented

2018-08-24 Thread Mariatta Wijaya
Mariatta Wijaya added the comment: New changeset 7b0ed43af55c1e2844aa0ccd5e088b2ddd38dbdb by Mariatta (Miss Islington (bot)) in branch '3.7': bpo-33550: Warn not to set SIGPIPE to SIG_DFL (GH-6773) https://github.com/python/cpython/commit/7b0ed43af55c1e2844aa0ccd5e088b2ddd38dbdb --

[issue33550] Sigpipe handling issue should be documented

2018-05-16 Thread Alfred Perlstein
New submission from Alfred Perlstein : 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