diff options
| author | Jeff Forcier <jeff@bitprophet.org> | 2023-01-16 21:25:52 -0500 |
|---|---|---|
| committer | Jeff Forcier <jeff@bitprophet.org> | 2023-01-16 21:33:25 -0500 |
| commit | 8367147e883583bba71cd660d1bae880a66eb27c (patch) | |
| tree | 5a40cde0c4f30faf6c66c5cc17919a0bcd577921 /sites | |
| parent | 53460723a6ab342129ac456ef6a4ba5ef676b577 (diff) | |
Nuke retry_on_signal, pointless on modern Py3
Additionally, other bits of code that retry EINTR can similarly just go
away.
Diffstat (limited to 'sites')
| -rw-r--r-- | sites/www/changelog.rst | 11 |
1 files changed, 11 insertions, 0 deletions
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 + <https://peps.python.org/pep-0475/>`_, 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 |