Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit b789c70

Browse files
freddrakefreddrake
committed
Minor markup nits.
1 parent f14e2f8 commit b789c70

2 files changed

Lines changed: 24 additions & 20 deletions

File tree

‎Doc/ext.tex‎

Lines changed: 12 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1309,9 +1309,11 @@ \chapter{Dynamic Loading}
13091309
configured, dynamic loading is trivial to use: when a Python program
13101310
executes \code{import spam}, the search for modules tries to find a
13111311
file \file{spammodule.o} (\file{spammodule.so} when using shared
1312-
libraries) in the module search path, and if one is found, it is
1313-
loaded into the executing binary and executed. Once loaded, the
1314-
module acts just like a built-in extension module.
1312+
libraries) in the module search path,%
1313+
\indexiii{module}{search}{path}
1314+
and if one is found, it is loaded into the executing binary and
1315+
executed. Once loaded, the module acts just like a built-in extension
1316+
module.
13151317

13161318
The advantages of dynamic loading are twofold: the ``core'' Python
13171319
binary gets smaller, and users can extend Python with their own
@@ -1411,10 +1413,10 @@ \section{Building a Dynamically Loadable Module}
14111413
Note that in all cases you will have to create your own Makefile that
14121414
compiles your module file(s). This Makefile will have to pass two
14131415
\samp{-I} arguments to the \C{} compiler which will make it find the
1414-
Python header files. If the Make variable \var{PYTHONTOP} points to
1415-
the toplevel Python directory, your \var{CFLAGS} Make variable should
1416+
Python header files. If the Make variable \makevar{PYTHONTOP} points to
1417+
the toplevel Python directory, your \makevar{CFLAGS} Make variable should
14161418
contain the options \samp{-I\$(PYTHONTOP) -I\$(PYTHONTOP)/Include}.
1417-
(Most header files are in the \file{Include} subdirectory, but the
1419+
(Most header files are in the \file{Include/} subdirectory, but the
14181420
\file{config.h} header lives in the toplevel directory.)
14191421

14201422

@@ -1461,7 +1463,8 @@ \subsection{SGI IRIX 4 Dynamic Loading}
14611463
assembler to generate position-independent code.
14621464

14631465
You don't need to link the resulting \file{spammodule.o} file; just
1464-
copy it into a directory along the Python module search path.
1466+
copy it into a directory along the Python module search path.%
1467+
\indexiii{module}{search}{path}
14651468

14661469
The first time your extension is loaded, it takes some extra time and
14671470
a few messages may be printed. This creates a file
@@ -1486,7 +1489,8 @@ \subsection{GNU Dynamic Loading}
14861489
\label{gnuLinking}
14871490

14881491
Just copy \file{spammodule.o} into a directory along the Python module
1489-
search path.
1492+
search path.%
1493+
\indexiii{module}{search}{path}
14901494

14911495
If your extension modules uses additional system libraries, you must
14921496
create a file \file{spammodule.libs} in the same directory as the
@@ -1495,6 +1499,4 @@ \subsection{GNU Dynamic Loading}
14951499
files). No \samp{-l} options can be used.
14961500

14971501

1498-
\input{ext.ind}
1499-
15001502
\end{document}

‎Doc/ext/ext.tex‎

Lines changed: 12 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1309,9 +1309,11 @@ \chapter{Dynamic Loading}
13091309
configured, dynamic loading is trivial to use: when a Python program
13101310
executes \code{import spam}, the search for modules tries to find a
13111311
file \file{spammodule.o} (\file{spammodule.so} when using shared
1312-
libraries) in the module search path, and if one is found, it is
1313-
loaded into the executing binary and executed. Once loaded, the
1314-
module acts just like a built-in extension module.
1312+
libraries) in the module search path,%
1313+
\indexiii{module}{search}{path}
1314+
and if one is found, it is loaded into the executing binary and
1315+
executed. Once loaded, the module acts just like a built-in extension
1316+
module.
13151317

13161318
The advantages of dynamic loading are twofold: the ``core'' Python
13171319
binary gets smaller, and users can extend Python with their own
@@ -1411,10 +1413,10 @@ \section{Building a Dynamically Loadable Module}
14111413
Note that in all cases you will have to create your own Makefile that
14121414
compiles your module file(s). This Makefile will have to pass two
14131415
\samp{-I} arguments to the \C{} compiler which will make it find the
1414-
Python header files. If the Make variable \var{PYTHONTOP} points to
1415-
the toplevel Python directory, your \var{CFLAGS} Make variable should
1416+
Python header files. If the Make variable \makevar{PYTHONTOP} points to
1417+
the toplevel Python directory, your \makevar{CFLAGS} Make variable should
14161418
contain the options \samp{-I\$(PYTHONTOP) -I\$(PYTHONTOP)/Include}.
1417-
(Most header files are in the \file{Include} subdirectory, but the
1419+
(Most header files are in the \file{Include/} subdirectory, but the
14181420
\file{config.h} header lives in the toplevel directory.)
14191421

14201422

@@ -1461,7 +1463,8 @@ \subsection{SGI IRIX 4 Dynamic Loading}
14611463
assembler to generate position-independent code.
14621464

14631465
You don't need to link the resulting \file{spammodule.o} file; just
1464-
copy it into a directory along the Python module search path.
1466+
copy it into a directory along the Python module search path.%
1467+
\indexiii{module}{search}{path}
14651468

14661469
The first time your extension is loaded, it takes some extra time and
14671470
a few messages may be printed. This creates a file
@@ -1486,7 +1489,8 @@ \subsection{GNU Dynamic Loading}
14861489
\label{gnuLinking}
14871490

14881491
Just copy \file{spammodule.o} into a directory along the Python module
1489-
search path.
1492+
search path.%
1493+
\indexiii{module}{search}{path}
14901494

14911495
If your extension modules uses additional system libraries, you must
14921496
create a file \file{spammodule.libs} in the same directory as the
@@ -1495,6 +1499,4 @@ \subsection{GNU Dynamic Loading}
14951499
files). No \samp{-l} options can be used.
14961500

14971501

1498-
\input{ext.ind}
1499-
15001502
\end{document}

0 commit comments

Comments
 (0)