Apply suggestions from code review

Author: XuehaiPan

Doc/library/sys.rst

@@ -26,13 +26,14 @@ always available. Unless explicitly noted otherwise, all variables are read-only
 
    .. versionchanged:: next
       A :exc:`DeprecationWarning` will be emitted if the :data:`sys.abiflags`
-      member is accessed on Windows before Python 3.16. The :data:`sys.abiflags`
+      member is accessed on Windows before Python 3.16. The :data:`!sys.abiflags`
       member will be set to a meaningful value on Windows in Python 3.16. This
-      means the :data:`sys.abiflags` member will always be available on all
+      means the :data:`!sys.abiflags` member will always be available on all
       platforms starting from Python 3.16.
 
-      See the notes for :ref:`incoming change to sys.abiflags <whatsnew314-sys-abiflags-change>`
-      in the *What's New* for more details.
+      See the notes for :ref:`incoming change to sys.abiflags
+      <whatsnew314-sys-abiflags-change>` on the *What's New in 3.14*
+      page for more details.
 
 
 .. function:: addaudithook(hook)

Doc/whatsnew/3.14.rst

@@ -930,10 +930,11 @@ sys
   It is always ``'freebsd'``, instead of ``'freebsd13'`` or ``'freebsd14'``.
 
 * Schedule a change for availability of :data:`sys.abiflags` on Windows. A
-  :exc:`DeprecationWarning` will be emitted if the :data:`sys.abiflags` member
+  :exc:`DeprecationWarning` will be emitted if the :data:`!sys.abiflags` member
   is accessed on Windows before Python 3.16.
   (Contributed by Xuehai Pan in :gh:`131717`.)
 
+
 .. _whatsnew314-sys-abiflags-change:
 
 sys.abiflags
@@ -966,11 +967,11 @@ To suppress this warning, use the :mod:`warnings` module:
 Due to historical reasons, :data:`sys.abiflags` is not covered by
 :pep:`3149` on Windows. Now we have multiple builds, such as the
 :term:`free-threaded <free threading>` build, that provide different ABIs.
-:data:`sys.abiflags` is now required under many circumstances to determine
+:data:`!sys.abiflags` is now required under many circumstances to determine
 the ABI of the Python interpreter.
 
-The :data:`sys.abiflags` member will be set to a meaningful value on
-Windows in Python 3.16. This means the :data:`sys.abiflags` member will
+The :data:`!sys.abiflags` member will be set to a meaningful value on
+Windows in Python 3.16. This means the :data:`!sys.abiflags` member will
 always be available on all platforms starting from Python 3.16.
 
 The following table shows how to migrate from the old code to the new code
@@ -986,6 +987,7 @@ without changing the behavior:
 | ``hasattr(sys, 'abiflags')``          | ``not sys.platform.startswith('win')``                              |
 +---------------------------------------+---------------------------------------------------------------------+
 
+
 sys.monitoring
 --------------
 

Python/sysmodule.c

@@ -113,7 +113,7 @@ _PySys_GetRequiredAttr(PyObject *name)
 #ifndef ABIFLAGS
         if (_PyUnicode_EqualToASCIIString(name, "abiflags")) {
             if (_warn_incoming_sys_abiflags_change() < 0) {
-                Py_XDECREF(value);
+                Py_CLEAR(value);
                 return NULL;
             }
         }
@@ -137,7 +137,7 @@ _PySys_GetRequiredAttrString(const char *name)
 #ifndef ABIFLAGS
         if (strcmp(name, "abiflags") == 0) {
             if (_warn_incoming_sys_abiflags_change() < 0) {
-                Py_XDECREF(value);
+                Py_CLEAR(value);
                 return NULL;
             }
         }
@@ -217,6 +217,7 @@ PySys_GetObject(const char *name)
 #ifndef ABIFLAGS
     if (ret == 0 && strcmp(name, "abiflags") == 0) {
         if (_warn_incoming_sys_abiflags_change() < 0) {
+            Py_CLEAR(value);
             return NULL;
         }
     }