diff options
author | Jeff Forcier <jeff@bitprophet.org> | 2023-01-09 19:32:57 -0500 |
---|---|---|
committer | Jeff Forcier <jeff@bitprophet.org> | 2023-01-09 23:26:00 -0500 |
commit | 3e87f05b57213cc539670f85ac7ea8ccddb9e5c4 (patch) | |
tree | 5f3442839198de82f1376dbc53a0916856a8ebb9 /sites | |
parent | 768f3e238b26127cee5cf5d4d18a17a40c349c9e (diff) |
Migrate some byte related helpers around
I feel like we should be able to just nuke byte_chr and friends at this
point, but it's not entirely obvious, so let's rock that boat later.
Diffstat (limited to 'sites')
-rw-r--r-- | sites/www/changelog.rst | 21 |
1 files changed, 14 insertions, 7 deletions
diff --git a/sites/www/changelog.rst b/sites/www/changelog.rst index 774cde27..595e2fde 100644 --- a/sites/www/changelog.rst +++ b/sites/www/changelog.rst @@ -2,21 +2,28 @@ Changelog ========= +- :support:`-` ``paramiko.common.asbytes`` has been moved to + `paramiko.util.asbytes`. + + .. warning:: + This change is backwards incompatible. + - :support:`-` Remove the now irrelevant ``paramiko.py3compat`` module. .. warning:: - This change is backwards incompatible if you were importing anything from - this module. Such references should be easily search-and-replaced with - their modern Python 3.6+ equivalents. + This change is backwards incompatible. Such references should be + search-and-replaced with their modern Python 3.6+ equivalents; in some + cases, still-useful methods or values have been moved to `paramiko.util` + (most) or `paramiko.common` (``byte_*``). - :support:`-` Drop support for Python versions less than 3.6, including Python 2. So long and thanks for all the fish! .. warning:: - This change is backwards compatible if you are still on older Python - versions. However, our packaging metadata has been updated to include - ``python_requires``, so this should not cause breakage unless you're on an - old installation method that can't read this metadata. + This change is backwards compatible. However, our packaging metadata has + been updated to include ``python_requires``, so this should not cause + breakage unless you're on an old installation method that can't read this + metadata. .. note:: As part of this change, our dependencies have been updated; eg we now |