From 8367147e883583bba71cd660d1bae880a66eb27c Mon Sep 17 00:00:00 2001 From: Jeff Forcier Date: Mon, 16 Jan 2023 21:25:52 -0500 Subject: Nuke retry_on_signal, pointless on modern Py3 Additionally, other bits of code that retry EINTR can similarly just go away. --- sites/www/changelog.rst | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'sites/www/changelog.rst') diff --git a/sites/www/changelog.rst b/sites/www/changelog.rst index 6df416a0..162d01bf 100644 --- a/sites/www/changelog.rst +++ b/sites/www/changelog.rst @@ -2,6 +2,17 @@ Changelog ========= +- :support:`-` ``paramiko.util.retry_on_signal`` (and any internal uses of + same, and also any internal retries of ``EINTR`` on eg socket operations) has + been removed. As of Python 3.5, per `PEP 475 + `_, this functionality (and retrying + ``EINTR`` generally) is now part of the standard library. + + .. warning:: + This change is backwards incompatible if you were explicitly + importing/using this particular function. The observable behavior otherwise + should not be changing. + - :support:`732` (also re: :issue:`630`) `~paramiko.config.SSHConfig` used to straight-up delete the ``proxycommand`` key from config lookup results when the source config said ``ProxyCommand none``. This has been altered to -- cgit v1.2.3