Skip to content

Commit

Permalink
Emend socket.connect markup
Browse files Browse the repository at this point in the history
  • Loading branch information
AA-Turner committed Sep 29, 2023
1 parent 9c73a9a commit 57f5b37
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions Doc/whatsnew/2.0.rst
Original file line number Diff line number Diff line change
Expand Up @@ -671,9 +671,9 @@ errors. If you absolutely must use 2.0 but can't fix your code, you can edit
``NO_STRICT_LIST_APPEND`` to preserve the old behaviour; this isn't recommended.

Some of the functions in the :mod:`socket` module are still forgiving in this
way. For example, :func:`socket.connect( ('hostname', 25) )` is the correct
form, passing a tuple representing an IP address, but :func:`socket.connect(
'hostname', 25 )` also works. :func:`socket.connect_ex` and :func:`socket.bind`
way. For example, ``socket.connect( ('hostname', 25) )`` is the correct
form, passing a tuple representing an IP address, but ``socket.connect('hostname', 25)``
also works. :func:`socket.connect_ex` and :func:`socket.bind`
are similarly easy-going. 2.0alpha1 tightened these functions up, but because
the documentation actually used the erroneous multiple argument form, many
people wrote code which would break with the stricter checking. GvR backed out
Expand Down

0 comments on commit 57f5b37

Please sign in to comment.