@@ -43,8 +43,8 @@ Initializing and finalizing the interpreter
4343
4444.. c :function :: void Py_InitializeEx (int initsigs)
4545
46- This function works like :c:func:`Py_Initialize` if *initsigs* is 1 . If
47- *initsigs* is 0 , it skips initialization registration of signal handlers, which
46+ This function works like :c:func:`Py_Initialize` if *initsigs* is ``1`` . If
47+ *initsigs* is ``0`` , it skips initialization registration of signal handlers, which
4848 might be useful when Python is embedded.
4949
5050 .. versionadded:: 2.4
@@ -295,7 +295,7 @@ Process-wide parameters
295295
296296 .. note::
297297 It is recommended that applications embedding the Python interpreter
298- for purposes other than executing a single script pass 0 as *updatepath*,
298+ for purposes other than executing a single script pass ``0`` as *updatepath*,
299299 and update :data:`sys.path` themselves if desired.
300300 See `CVE-2008-5983 <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5983>`_.
301301
@@ -307,13 +307,13 @@ Process-wide parameters
307307
308308 .. versionadded:: 2.6.6
309309
310- .. XXX impl. doesn't seem consistent in allowing 0/ NULL for the params;
310+ .. XXX impl. doesn't seem consistent in allowing ``0``/`` NULL`` for the params;
311311 check w/ Guido.
312312
313313
314314.. c:function:: void PySys_SetArgv(int argc, char **argv)
315315
316- This function works like :c:func:`PySys_SetArgvEx` with *updatepath* set to 1 .
316+ This function works like :c:func:`PySys_SetArgvEx` with *updatepath* set to ``1`` .
317317
318318
319319.. c:function:: void Py_SetPythonHome(char *home)
@@ -917,8 +917,8 @@ pointer and a void pointer argument.
917917 .. index:: single: Py_AddPendingCall()
918918
919919 Schedule a function to be called from the main interpreter thread. On
920- success, 0 is returned and *func* is queued for being called in the
921- main thread. On failure, -1 is returned without setting any exception.
920+ success, ``0`` is returned and *func* is queued for being called in the
921+ main thread. On failure, ``-1`` is returned without setting any exception.
922922
923923 When successfully queued, *func* will be *eventually* called from the
924924 main interpreter thread with the argument *arg*. It will be called
@@ -929,7 +929,7 @@ pointer and a void pointer argument.
929929 * with the main thread holding the :term:`global interpreter lock`
930930 (*func* can therefore use the full C API).
931931
932- *func* must return 0 on success, or -1 on failure with an exception
932+ *func* must return ``0`` on success, or ``-1`` on failure with an exception
933933 set. *func* won't be interrupted to perform another asynchronous
934934 notification recursively, but it can still be interrupted to switch
935935 threads if the global interpreter lock is released.
0 commit comments