@@ -44,8 +44,8 @@ Initializing and finalizing the interpreter
4444
4545.. c :function :: void Py_InitializeEx (int initsigs)
4646
47- This function works like :c:func:`Py_Initialize` if *initsigs* is 1 . If
48- *initsigs* is 0 , it skips initialization registration of signal handlers, which
47+ This function works like :c:func:`Py_Initialize` if *initsigs* is ``1`` . If
48+ *initsigs* is ``0`` , it skips initialization registration of signal handlers, which
4949 might be useful when Python is embedded.
5050
5151
@@ -114,7 +114,7 @@ Process-wide parameters
114114 If :c:func:`Py_Finalize` is called, this function will need to be called
115115 again in order to affect subsequent calls to :c:func:`Py_Initialize`.
116116
117- Returns 0 if successful, a nonzero value on error (e.g. calling after the
117+ Returns ``0`` if successful, a nonzero value on error (e.g. calling after the
118118 interpreter has already been initialized).
119119
120120 .. versionadded:: 3.4
@@ -349,7 +349,7 @@ Process-wide parameters
349349 - If the name of an existing script is passed in ``argv[0] ``, the absolute
350350 path of the directory where the script is located is prepended to
351351 :data: `sys.path `.
352- - Otherwise (that is, if *argc * is 0 or ``argv[0] `` doesn't point
352+ - Otherwise (that is, if *argc * is `` 0 `` or ``argv[0] `` doesn't point
353353 to an existing file name), an empty string is prepended to
354354 :data: `sys.path `, which is the same as prepending the current working
355355 directory (``"." ``).
@@ -359,7 +359,7 @@ Process-wide parameters
359359
360360 .. note ::
361361 It is recommended that applications embedding the Python interpreter
362- for purposes other than executing a single script pass 0 as *updatepath *,
362+ for purposes other than executing a single script pass `` 0 `` as *updatepath *,
363363 and update :data: `sys.path ` themselves if desired.
364364 See `CVE-2008-5983 <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5983 >`_.
365365
@@ -371,14 +371,14 @@ Process-wide parameters
371371
372372 .. versionadded :: 3.1.3
373373
374- .. XXX impl. doesn't seem consistent in allowing 0/ NULL for the params;
374+ .. XXX impl. doesn't seem consistent in allowing ``0``/`` NULL`` for the params;
375375 check w/ Guido.
376376
377377
378378 .. c :function :: void PySys_SetArgv (int argc, wchar_t **argv)
379379
380380 This function works like :c:func: `PySys_SetArgvEx ` with *updatepath * set
381- to 1 unless the :program: `python ` interpreter was started with the
381+ to `` 1 `` unless the :program: `python ` interpreter was started with the
382382 :option: `-I `.
383383
384384 Use :c:func: `Py_DecodeLocale ` to decode a bytes string to get a
@@ -718,10 +718,10 @@ with sub-interpreters:
718718
719719.. c:function:: int PyGILState_Check()
720720
721- Return 1 if the current thread is holding the GIL and 0 otherwise.
721+ Return ``1`` if the current thread is holding the GIL and ``0`` otherwise.
722722 This function can be called from any thread at any time.
723723 Only if it has had its Python thread state initialized and currently is
724- holding the GIL will it return 1 .
724+ holding the GIL will it return ``1`` .
725725 This is mainly a helper/diagnostic function. It can be useful
726726 for example in callback contexts or memory allocation functions when
727727 knowing that the GIL is locked can allow the caller to perform sensitive
@@ -991,8 +991,8 @@ pointer and a void pointer argument.
991991 .. index :: single: Py_AddPendingCall()
992992
993993 Schedule a function to be called from the main interpreter thread. On
994- success, 0 is returned and *func * is queued for being called in the
995- main thread. On failure, -1 is returned without setting any exception.
994+ success, `` 0 `` is returned and *func * is queued for being called in the
995+ main thread. On failure, `` -1 `` is returned without setting any exception.
996996
997997 When successfully queued, *func * will be *eventually * called from the
998998 main interpreter thread with the argument *arg *. It will be called
@@ -1003,7 +1003,7 @@ pointer and a void pointer argument.
10031003 * with the main thread holding the :term: `global interpreter lock `
10041004 (*func * can therefore use the full C API).
10051005
1006- *func* must return 0 on success, or -1 on failure with an exception
1006+ *func* must return ``0`` on success, or ``-1`` on failure with an exception
10071007 set. *func* won't be interrupted to perform another asynchronous
10081008 notification recursively, but it can still be interrupted to switch
10091009 threads if the global interpreter lock is released.
0 commit comments