update docutils refs

Author: picnixz

Doc/c-api/init.rst

@@ -94,8 +94,8 @@ and options. By default, these flags are controlled by :ref:`command line
 options <using-on-interface-options>`.
 
 When a flag is set by an option, the value of the flag is the number of times
-that the option was set. For example, ``-b`` sets :c:data:`Py_BytesWarningFlag`
-to 1 and ``-bb`` sets :c:data:`Py_BytesWarningFlag` to 2.
+that the option was set. For example, ``-b`` sets :c:attr:`PyConfig.bytes_warning`
+to 1 and ``-bb`` sets :c:attr:`PyConfig.bytes_warning` to 2.
 
 
 .. c:var:: int Py_InteractiveFlag

Doc/whatsnew/3.12.rst

@@ -2150,24 +2150,24 @@ Deprecated
 
 * Deprecate global configuration variable:
 
-  * :c:var:`Py_DebugFlag`: use :c:member:`PyConfig.parser_debug`
-  * :c:var:`Py_VerboseFlag`: use :c:member:`PyConfig.verbose`
-  * :c:var:`Py_QuietFlag`: use :c:member:`PyConfig.quiet`
-  * :c:var:`Py_InteractiveFlag`: use :c:member:`PyConfig.interactive`
-  * :c:var:`Py_InspectFlag`: use :c:member:`PyConfig.inspect`
-  * :c:var:`Py_OptimizeFlag`: use :c:member:`PyConfig.optimization_level`
-  * :c:var:`Py_NoSiteFlag`: use :c:member:`PyConfig.site_import`
-  * :c:var:`Py_BytesWarningFlag`: use :c:member:`PyConfig.bytes_warning`
-  * :c:var:`Py_FrozenFlag`: use :c:member:`PyConfig.pathconfig_warnings`
-  * :c:var:`Py_IgnoreEnvironmentFlag`: use :c:member:`PyConfig.use_environment`
-  * :c:var:`Py_DontWriteBytecodeFlag`: use :c:member:`PyConfig.write_bytecode`
-  * :c:var:`Py_NoUserSiteDirectory`: use :c:member:`PyConfig.user_site_directory`
-  * :c:var:`Py_UnbufferedStdioFlag`: use :c:member:`PyConfig.buffered_stdio`
-  * :c:var:`Py_HashRandomizationFlag`: use :c:member:`PyConfig.use_hash_seed`
+  * :c:var:`!Py_DebugFlag`: use :c:member:`PyConfig.parser_debug`
+  * :c:var:`!Py_VerboseFlag`: use :c:member:`PyConfig.verbose`
+  * :c:var:`!Py_QuietFlag`: use :c:member:`PyConfig.quiet`
+  * :c:var:`!Py_InteractiveFlag`: use :c:member:`PyConfig.interactive`
+  * :c:var:`!Py_InspectFlag`: use :c:member:`PyConfig.inspect`
+  * :c:var:`!Py_OptimizeFlag`: use :c:member:`PyConfig.optimization_level`
+  * :c:var:`!Py_NoSiteFlag`: use :c:member:`PyConfig.site_import`
+  * :c:var:`!Py_BytesWarningFlag`: use :c:member:`PyConfig.bytes_warning`
+  * :c:var:`!Py_FrozenFlag`: use :c:member:`PyConfig.pathconfig_warnings`
+  * :c:var:`!Py_IgnoreEnvironmentFlag`: use :c:member:`PyConfig.use_environment`
+  * :c:var:`!Py_DontWriteBytecodeFlag`: use :c:member:`PyConfig.write_bytecode`
+  * :c:var:`!Py_NoUserSiteDirectory`: use :c:member:`PyConfig.user_site_directory`
+  * :c:var:`!Py_UnbufferedStdioFlag`: use :c:member:`PyConfig.buffered_stdio`
+  * :c:var:`!Py_HashRandomizationFlag`: use :c:member:`PyConfig.use_hash_seed`
     and :c:member:`PyConfig.hash_seed`
-  * :c:var:`Py_IsolatedFlag`: use :c:member:`PyConfig.isolated`
-  * :c:var:`Py_LegacyWindowsFSEncodingFlag`: use :c:member:`PyPreConfig.legacy_windows_fs_encoding`
-  * :c:var:`Py_LegacyWindowsStdioFlag`: use :c:member:`PyConfig.legacy_windows_stdio`
+  * :c:var:`!Py_IsolatedFlag`: use :c:member:`PyConfig.isolated`
+  * :c:var:`!Py_LegacyWindowsFSEncodingFlag`: use :c:member:`PyPreConfig.legacy_windows_fs_encoding`
+  * :c:var:`!Py_LegacyWindowsStdioFlag`: use :c:member:`PyConfig.legacy_windows_stdio`
   * :c:var:`!Py_FileSystemDefaultEncoding`: use :c:member:`PyConfig.filesystem_encoding`
   * :c:var:`!Py_HasFileSystemDefaultEncoding`: use :c:member:`PyConfig.filesystem_encoding`
   * :c:var:`!Py_FileSystemDefaultEncodeErrors`: use :c:member:`PyConfig.filesystem_errors`

Doc/whatsnew/3.7.rst

@@ -2517,7 +2517,7 @@ number of other issues). Some known details affected:
   over the default filters set by the interpreter
 
 Due to changes in the way the default warnings filters are configured,
-setting :c:data:`Py_BytesWarningFlag` to a value greater than one is no longer
+setting :c:data:`!Py_BytesWarningFlag` to a value greater than one is no longer
 sufficient to both emit :exc:`BytesWarning` messages and have them converted
 to exceptions.  Instead, the flag must be set (to cause the warnings to be
 emitted in the first place), and an explicit ``error::BytesWarning``
@@ -2540,7 +2540,7 @@ Starting in 3.7.1, :c:func:`Py_Initialize` now consistently reads and respects
 all of the same environment settings as :c:func:`Py_Main` (in earlier Python
 versions, it respected an ill-defined subset of those environment variables,
 while in Python 3.7.0 it didn't read any of them due to :issue:`34247`). If
-this behavior is unwanted, set :c:data:`Py_IgnoreEnvironmentFlag` to 1 before
+this behavior is unwanted, set :c:data:`!Py_IgnoreEnvironmentFlag` to 1 before
 calling :c:func:`Py_Initialize`.
 
 In 3.7.1 the C API for Context Variables

Misc/NEWS.d/3.12.0a1.rst

@@ -6089,7 +6089,7 @@ Patch by Serge Guelton.
 .. section: C API
 
 Deprecate global configuration variables, like
-:c:var:`Py_IgnoreEnvironmentFlag`, in the documentation: the
+:c:var:`!Py_IgnoreEnvironmentFlag`, in the documentation: the
 :c:func:`Py_InitializeFromConfig` API should be instead. Patch by Victor
 Stinner.
 
@@ -6101,7 +6101,7 @@ Stinner.
 .. section: C API
 
 Deprecate global configuration variable like
-:c:var:`Py_IgnoreEnvironmentFlag`: the :c:func:`Py_InitializeFromConfig` API
+:c:var:`!Py_IgnoreEnvironmentFlag`: the :c:func:`Py_InitializeFromConfig` API
 should be instead. Patch by Victor Stinner.
 
 ..