Mention ssl.SSLObject in the NEWS entry

Author: vstinner

Misc/NEWS.d/next/Library/2026-04-28-17-47-55.gh-issue-148292.oIq3ml.rst

@@ -1,7 +1,7 @@
-:mod:`ssl`: Update :class:`ssl.SSLSocket` for OpenSSL 4. The class now
-remembers if it gets a :exc:`ssl.SSLEOFError`. In this case, following
-:meth:`~ssl.SSLSocket.read`, :meth:`!sendfile`, :meth:`~ssl.SSLSocket.write`,
-and :meth:`~ssl.SSLSocket.do_handshake` calls raise :exc:`ssl.SSLEOFError`
-without calling the underlying OpenSSL function. Thanks to that,
-:class:`ssl.SSLSocket` behaves the same on all OpenSSL versions on EOF.  Patch
-by Victor Stinner.
+:mod:`ssl`: Update :class:`ssl.SSLSocket` and :class:`ssl.SSLObject` for
+OpenSSL 4. The class now remembers if it gets a :exc:`ssl.SSLEOFError`. In this
+case, following :meth:`~ssl.SSLSocket.read`, :meth:`!sendfile`,
+:meth:`~ssl.SSLSocket.write`, and :meth:`~ssl.SSLSocket.do_handshake` calls
+raise :exc:`ssl.SSLEOFError` without calling the underlying OpenSSL function.
+Thanks to that, :class:`ssl.SSLSocket` behaves the same on all OpenSSL versions
+on EOF.  Patch by Victor Stinner.

Modules/_ssl.c

@@ -377,9 +377,9 @@ typedef struct {
     enum py_ssl_server_or_client socket_type;
     PyObject *owner; /* weakref to Python level "owner" passed to servername callback */
     PyObject *server_hostname;
-    // gh-148292: If non-zero, read(), sendfile() and write() methods raise
-    // SSLEOFError without calling the underlying OpenSSL function. Set to 1
-    // on PY_SSL_ERROR_EOF error.
+    // gh-148292: If non-zero, read(), sendfile(), write() and do_handshake()
+    // methods raise SSLEOFError without calling the underlying OpenSSL
+    // function. Set to 1 on PY_SSL_ERROR_EOF error.
     //
     // On OpenSSL 4, if SSL_read_ex() fails with
     // SSL_R_UNEXPECTED_EOF_WHILE_READING, the following SSL_read_ex() call