[issue35753] Importing call from unittest.mock directly causes ValueError

2021-03-14 Thread Alfred Perlstein
Alfred Perlstein added the comment: I have a patch here that fixes this: https://github.com/python/cpython/pull/22981 It simply swallows the unwrap exception making doctest immune to such buggy objects. Can someone help it get reviewed please

[issue35753] Importing call from unittest.mock directly causes ValueError

2020-10-25 Thread Alfred Perlstein
Change by Alfred Perlstein : -- pull_requests: +21898 pull_request: https://github.com/python/cpython/pull/22981 ___ Python tracker <https://bugs.python.org/issue35

[issue35753] Importing call from unittest.mock directly causes ValueError

2020-10-20 Thread Alfred Perlstein
Change by Alfred Perlstein : -- keywords: +patch nosy: +splbio nosy_count: 4.0 -> 5.0 pull_requests: +21788 stage: resolved -> patch review pull_request: https://github.com/python/cpython/pull/22834 ___ Python tracker <https://bugs.p

[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 lifetime. (