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

Skip to content

Commit 2e56c8a

Browse files
nnorwitznnorwitz
committed
SF #1005913, Patch to allow building of paper-*/dist.pdf by Jeff Epler
There were subsections without sections, so drop a sub.
1 parent ee6511b commit 2e56c8a

1 file changed

Lines changed: 27 additions & 27 deletions

File tree

‎Doc/dist/dist.tex‎

Lines changed: 27 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -314,7 +314,7 @@ \chapter{Writing the Setup Script}
314314
\end{verbatim}
315315

316316

317-
\subsection{Listing whole packages}
317+
\section{Listing whole packages}
318318
\label{listing-packages}
319319

320320
The \option{packages} option tells the Distutils to process (build,
@@ -369,7 +369,7 @@ \subsection{Listing whole packages}
369369
\file{\_\_init\_\_.py} file.)
370370

371371

372-
\subsection{Listing individual modules}
372+
\section{Listing individual modules}
373373
\label{listing-modules}
374374

375375
For a small module distribution, you might prefer to list all modules
@@ -390,7 +390,7 @@ \subsection{Listing individual modules}
390390
the \option{package\_dir} option.
391391

392392

393-
\subsection{Describing extension modules}
393+
\section{Describing extension modules}
394394
\label{describing-extensions}
395395

396396
% XXX read over this section
@@ -433,7 +433,7 @@ \subsection{Describing extension modules}
433433
explained in the following sections.
434434

435435

436-
\subsubsection{Extension names and packages}
436+
\subsection{Extension names and packages}
437437

438438
The first argument to the \class{Extension} constructor is always the
439439
name of the extension, including any package names. For example,
@@ -469,7 +469,7 @@ \subsubsection{Extension names and packages}
469469
\file{bar.c} to \module{pkg.subpkg.bar}.
470470

471471

472-
\subsubsection{Extension source files}
472+
\subsection{Extension source files}
473473

474474
The second argument to the \class{Extension} constructor is a list of
475475
source files. Since the Distutils currently only support C, \Cpp, and
@@ -494,7 +494,7 @@ \subsubsection{Extension source files}
494494
(\file{.res}) files and linked into the executable.
495495

496496

497-
\subsubsection{Preprocessor options}
497+
\subsection{Preprocessor options}
498498

499499
Three optional arguments to \class{Extension} will help if you need to
500500
specify include directories to search or preprocessor macros to
@@ -581,7 +581,7 @@ \subsubsection{Preprocessor options}
581581
\end{verbatim}
582582

583583

584-
\subsubsection{Library options}
584+
\subsection{Library options}
585585

586586
You can also specify the libraries to link against when building your
587587
extension, and the directories to search for those libraries. The
@@ -612,7 +612,7 @@ \subsubsection{Library options}
612612

613613
\XXX{Should mention clib libraries here or somewhere else!}
614614

615-
\subsubsection{Other options}
615+
\subsection{Other options}
616616

617617
There are still some other options which can be used to handle special
618618
cases.
@@ -631,7 +631,7 @@ \subsubsection{Other options}
631631
will automatically add \code{initmodule}
632632
to the list of exported symbols.
633633

634-
\subsection{Installing Scripts}
634+
\section{Installing Scripts}
635635
So far we have been dealing with pure and non-pure Python modules,
636636
which are usually not run by themselves but imported by scripts.
637637

@@ -652,7 +652,7 @@ \subsection{Installing Scripts}
652652
\end{verbatim}
653653

654654

655-
\subsection{Installing Package Data}
655+
\section{Installing Package Data}
656656

657657
Often, additional files need to be installed into a package. These
658658
files are often data that's closely related to the package's
@@ -701,7 +701,7 @@ \subsection{Installing Package Data}
701701
\versionadded{2.4}
702702

703703

704-
\subsection{Installing Additional Files}
704+
\section{Installing Additional Files}
705705

706706
The \option{data\_files} option can be used to specify additional
707707
files needed by the module distribution: configuration files, message
@@ -739,7 +739,7 @@ \subsection{Installing Additional Files}
739739
To install data files directly in the target directory, an empty
740740
string should be given as the directory.
741741

742-
\subsection{Additional meta-data}
742+
\section{Additional meta-data}
743743
\label{meta-data}
744744

745745
The setup script may include additional meta-data beyond the name and
@@ -846,7 +846,7 @@ \subsection{Additional meta-data}
846846
\end{verbatim}
847847

848848

849-
\subsection{Debugging the setup script}
849+
\section{Debugging the setup script}
850850

851851
Sometimes things go wrong, and the setup script doesn't do what the
852852
developer wants.
@@ -1051,7 +1051,7 @@ \chapter{Creating a Source Distribution}
10511051

10521052

10531053

1054-
\subsection{Specifying the files to distribute}
1054+
\section{Specifying the files to distribute}
10551055
\label{manifest}
10561056

10571057
If you don't supply an explicit list of files (or instructions on how to
@@ -1156,7 +1156,7 @@ \subsection{Specifying the files to distribute}
11561156
That way, the manifest template is portable across operating systems.
11571157

11581158

1159-
\subsection{Manifest-related options}
1159+
\section{Manifest-related options}
11601160
\label{manifest-options}
11611161

11621162
The normal course of operations for the \command{sdist} command is as
@@ -1324,14 +1324,14 @@ \chapter{Creating Built Distributions}
13241324
commands.
13251325

13261326

1327-
\subsection{Creating dumb built distributions}
1327+
\section{Creating dumb built distributions}
13281328
\label{creating-dumb}
13291329

13301330
\XXX{Need to document absolute vs. prefix-relative packages here, but
13311331
first I have to implement it!}
13321332

13331333

1334-
\subsection{Creating RPM packages}
1334+
\section{Creating RPM packages}
13351335
\label{creating-rpms}
13361336

13371337
The RPM format is used by many popular Linux distributions, including
@@ -1455,7 +1455,7 @@ \subsection{Creating RPM packages}
14551455
% to the \file{.spec} file.)
14561456

14571457

1458-
\subsection{Creating Windows Installers}
1458+
\section{Creating Windows Installers}
14591459
\label{creating-wininst}
14601460

14611461
Executable installers are the natural format for binary distributions
@@ -1508,7 +1508,7 @@ \subsection{Creating Windows Installers}
15081508
--- normally \file{dist/}, but customizable with the
15091509
\longprogramopt{dist-dir} option.
15101510

1511-
\subsubsection{The Postinstallation script}
1511+
\subsection{The Postinstallation script}
15121512
\label{postinstallation-script}
15131513

15141514
Starting with Python 2.3, a postinstallation script can be specified
@@ -1982,7 +1982,7 @@ \chapter{Command Reference}
19821982
\label{reference}
19831983

19841984

1985-
%\subsection{Building modules: the \protect\command{build} command family}
1985+
%\section{Building modules: the \protect\command{build} command family}
19861986
%\label{build-cmds}
19871987

19881988
%\subsubsection{\protect\command{build}}
@@ -3510,41 +3510,41 @@ \section{\module{distutils.command.config} --- Perform package configuration}
35103510

35113511
% todo
35123512

3513-
\subsubsection{\module{distutils.command.install} --- Install a package}
3513+
\section{\module{distutils.command.install} --- Install a package}
35143514
\declaremodule{standard}{distutils.command.install}
35153515
\modulesynopsis{Install a package}
35163516

35173517
% todo
35183518

3519-
\subsubsection{\module{distutils.command.install_data}
3519+
\section{\module{distutils.command.install_data}
35203520
--- Install data files from a package}
35213521
\declaremodule[distutils.command.installdata]{standard}{distutils.command.install_data}
35223522
\modulesynopsis{Install data files from a package}
35233523

35243524
% todo
35253525

3526-
\subsubsection{\module{distutils.command.install_headers}
3526+
\section{\module{distutils.command.install_headers}
35273527
--- Install C/\Cpp{} header files from a package}
35283528
\declaremodule[distutils.command.installheaders]{standard}{distutils.command.install_headers}
35293529
\modulesynopsis{Install C/\Cpp{} header files from a package}
35303530

35313531
% todo
35323532

3533-
\subsubsection{\module{distutils.command.install_lib}
3533+
\section{\module{distutils.command.install_lib}
35343534
--- Install library files from a package}
35353535
\declaremodule[distutils.command.installlib]{standard}{distutils.command.install_lib}
35363536
\modulesynopsis{Install library files from a package}
35373537

35383538
% todo
35393539

3540-
\subsubsection{\module{distutils.command.install_scripts}
3540+
\section{\module{distutils.command.install_scripts}
35413541
--- Install script files from a package}
35423542
\declaremodule[distutils.command.installscripts]{standard}{distutils.command.install_scripts}
35433543
\modulesynopsis{Install script files from a package}
35443544

35453545
% todo
35463546

3547-
\subsubsection{\module{distutils.command.register}
3547+
\section{\module{distutils.command.register}
35483548
--- Register a module with the Python Package Index}
35493549
\declaremodule{standard}{distutils.command.register}
35503550
\modulesynopsis{Register a module with the Python Package Index}
@@ -3553,7 +3553,7 @@ \subsubsection{\module{distutils.command.register}
35533553
Index. This is described in more detail in \pep{301}.
35543554
% todo
35553555

3556-
\subsubsection{Creating a new Distutils command}
3556+
\section{Creating a new Distutils command}
35573557

35583558
This section outlines the steps to create a new Distutils command.
35593559

0 commit comments

Comments
 (0)