mirror of
https://github.com/python/cpython
synced 2024-09-05 00:05:39 +00:00
bpo-36384: [doc] Mention CVE-2021-29921 fix in 3.8.12 (GH-27824)
This commit is contained in:
parent
942d1a4284
commit
0fd66e46b2
|
@ -132,6 +132,11 @@ write code that handles both IP versions correctly. Address objects are
|
|||
The above change was also included in Python 3.9 starting with
|
||||
version 3.9.5.
|
||||
|
||||
.. versionchanged:: 3.8.12
|
||||
|
||||
The above change was also included in Python 3.8 starting with
|
||||
version 3.8.12.
|
||||
|
||||
.. attribute:: version
|
||||
|
||||
The appropriate version number: ``4`` for IPv4, ``6`` for IPv6.
|
||||
|
|
|
@ -2248,3 +2248,16 @@ separator key, with ``&`` as the default. This change also affects
|
|||
functions internally. For more details, please see their respective
|
||||
documentation.
|
||||
(Contributed by Adam Goldschmidt, Senthil Kumaran and Ken Jin in :issue:`42967`.)
|
||||
|
||||
Notable changes in Python 3.8.12
|
||||
================================
|
||||
|
||||
Starting with Python 3.8.12 the :mod:`ipaddress` module no longer accepts
|
||||
any leading zeros in IPv4 address strings. Leading zeros are ambiguous and
|
||||
interpreted as octal notation by some libraries. For example the legacy
|
||||
function :func:`socket.inet_aton` treats leading zeros as octal notation.
|
||||
glibc implementation of modern :func:`~socket.inet_pton` does not accept
|
||||
any leading zeros.
|
||||
|
||||
(Originally contributed by Christian Heimes in :issue:`36384`, and backported
|
||||
to 3.8 by Achraf Merzouki.)
|
||||
|
|
Loading…
Reference in a new issue