@@ -69,10 +69,12 @@ standard headers) have one of the prefixes ``Py`` or ``_Py``. Names beginning
69
69
with ``_Py `` are for internal use by the Python implementation and should not be
70
70
used by extension writers. Structure member names do not have a reserved prefix.
71
71
72
- **Important: ** user code should never define names that begin with ``Py `` or
73
- ``_Py ``. This confuses the reader, and jeopardizes the portability of the user
74
- code to future Python versions, which may define additional names beginning with
75
- one of these prefixes.
72
+ .. note ::
73
+
74
+ User code should never define names that begin with ``Py `` or ``_Py ``. This
75
+ confuses the reader, and jeopardizes the portability of the user code to
76
+ future Python versions, which may define additional names beginning with one
77
+ of these prefixes.
76
78
77
79
The header files are typically installed with Python. On Unix, these are
78
80
located in the directories :file: `{ prefix } /include/pythonversion/ ` and
@@ -90,9 +92,9 @@ multi-platform builds since the platform independent headers under
90
92
:envvar: `prefix ` include the platform specific headers from
91
93
:envvar: `exec_prefix `.
92
94
93
- C++ users should note that though the API is defined entirely using C, the
94
- header files do properly declare the entry points to be ``extern "C" ``, so there
95
- is no need to do anything special to use the API from C++.
95
+ C++ users should note that although the API is defined entirely using C, the
96
+ header files properly declare the entry points to be ``extern "C" ``. As a result,
97
+ there is no need to do anything special to use the API from C++.
96
98
97
99
98
100
Useful macros
0 commit comments