summaryrefslogtreecommitdiffstats
path: root/Doc/c-api/concrete.rst
diff options
context:
space:
mode:
authorSerhiy Storchaka <storchaka@gmail.com>2019-10-30 10:03:20 (GMT)
committerGitHub <noreply@github.com>2019-10-30 10:03:20 (GMT)
commit25fc088607c855060ed142296dc1bd0125fad1af (patch)
tree384af093a75c0d66a00da4b1d2b184e68de67211 /Doc/c-api/concrete.rst
parentda6ce58dd5ac109485af45878fca6bfd265b43e9 (diff)
downloadcpython-25fc088607c855060ed142296dc1bd0125fad1af.zip
cpython-25fc088607c855060ed142296dc1bd0125fad1af.tar.gz
cpython-25fc088607c855060ed142296dc1bd0125fad1af.tar.bz2
bpo-38600: Change the mark up of NULL in the C API documentation. (GH-16950)
Replace all *NULL* with ``NULL``.
Diffstat (limited to 'Doc/c-api/concrete.rst')
-rw-r--r--Doc/c-api/concrete.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/Doc/c-api/concrete.rst b/Doc/c-api/concrete.rst
index f83d711..c1d9fa1 100644
--- a/Doc/c-api/concrete.rst
+++ b/Doc/c-api/concrete.rst
@@ -17,8 +17,8 @@ dictionary, use :c:func:`PyDict_Check`. The chapter is structured like the
.. warning::
While the functions described in this chapter carefully check the type of the
- objects which are passed in, many of them do not check for *NULL* being passed
- instead of a valid object. Allowing *NULL* to be passed in can cause memory
+ objects which are passed in, many of them do not check for ``NULL`` being passed
+ instead of a valid object. Allowing ``NULL`` to be passed in can cause memory
access violations and immediate termination of the interpreter.