source: vendor/python/2.5/Doc/README

Last change on this file was 3225, checked in by bird, 18 years ago

Python 2.5

File size: 9.2 KB
Line 
1Python standard documentation -- in LaTeX
2-----------------------------------------
3
4This directory contains the LaTeX sources to the Python documentation
5and tools required to support the formatting process. The documents
6now require LaTeX2e; LaTeX 2.09 compatibility has been dropped.
7
8If you don't have LaTeX, or if you'd rather not format the
9documentation yourself, you can ftp a tar file containing HTML, PDF,
10or PostScript versions of all documents. Additional formats may be
11available. These should be in the same place where you fetched the
12main Python distribution (try <http://www.python.org/> or
13<ftp://ftp.python.org/pub/python/>).
14
15The following are the LaTeX source files:
16
17 api/*.tex Python/C API Reference Manual
18 doc/*.tex Documenting Python
19 ext/*.tex Extending and Embedding the Python Interpreter
20 lib/*.tex Python Library Reference
21 mac/*.tex Macintosh Library Modules
22 ref/*.tex Python Reference Manual
23 tut/*.tex Python Tutorial
24 inst/*.tex Installing Python Modules
25 dist/*.tex Distributing Python Modules
26
27Most use the "manual" document class and "python" package, derived from
28the old "myformat.sty" style file. The Macintosh Library Modules
29document uses the "howto" document class instead. These contains many
30macro definitions useful in documenting Python, and set some style
31parameters.
32
33There's a Makefile to call LaTeX and the other utilities in the right
34order and the right number of times. By default, it will build the
35HTML version of the documentation, but DVI, PDF, and PostScript can
36also be made. To view the generated HTML, point your favorite browser
37at the top-level index (html/index.html) after running "make".
38
39The Makefile can also produce DVI files for each document made; to
40preview them, use xdvi. PostScript is produced by the same Makefile
41target that produces the DVI files. This uses the dvips tool.
42Printing depends on local conventions; at our site, we use lpr. For
43example:
44
45 make paper-letter/lib.ps # create lib.dvi and lib.ps
46 xdvi paper-letter/lib.dvi # preview lib.dvi
47 lpr paper-letter/lib.ps # print on default printer
48
49
50What if I find a bug?
51---------------------
52
53First, check that the bug is present in the development version of the
54documentation at <http://www.python.org/dev/doc/devel/>; we may
55have already fixed it.
56
57If we haven't, tell us about it. We'd like the documentation to be
58complete and accurate, but have limited time. If you discover any
59inconsistencies between the documentation and implementation, or just
60have suggestions as to how to improve the documentation, let is know!
61Specific bugs and patches should be reported using our bug & patch
62databases at:
63
64 http://sourceforge.net/projects/python
65
66Other suggestions or questions should be sent to the Python
67Documentation Team:
68
69 docs@python.org
70
71Thanks!
72
73
74What tools do I need?
75---------------------
76
77You need to install Python; some of the scripts used to produce the
78documentation are written in Python. You don't need this
79documentation to install Python; instructions are included in the
80README file in the Python distribution.
81
82The simplest way to get the rest of the tools in the configuration we
83used is to install the teTeX TeX distribution, versions 0.9 or newer.
84More information is available on teTeX at <http://www.tug.org/tetex/>.
85This is a Unix-only TeX distribution at this time. This documentation
86release was tested with the 1.0.7 release, but there have been no
87substantial changes since late in the 0.9 series, which we used
88extensively for previous versions without any difficulty.
89
90If you don't want to get teTeX, here is what you'll need:
91
92To create DVI, PDF, or PostScript files:
93
94 - LaTeX2e, 1995/12/01 or newer. Older versions are likely to
95 choke.
96
97 - makeindex. This is used to produce the indexes for the
98 library reference and Python/C API reference.
99
100To create PDF files:
101
102 - pdflatex. We used the one in the teTeX distribution (pdfTeX
103 version 3.14159-13d (Web2C 7.3.1) at the time of this
104 writing). Versions even a couple of patchlevels earlier are
105 highly likely to fail due to syntax changes for some of the
106 pdftex primitives.
107
108To create PostScript files:
109
110 - dvips. Most TeX installations include this. If you don't
111 have one, check CTAN (<ftp://ctan.tug.org/tex-archive/>).
112
113To create info files:
114
115 Note that info support is currently being revised using new
116 conversion tools by Michael Ernst <mernst@cs.washington.edu>.
117
118 - makeinfo. This is available from any GNU mirror.
119
120 - emacs or xemacs. Emacs is available from the same place as
121 makeinfo, and xemacs is available from ftp.xemacs.org.
122
123 - Perl. Find the software at
124 <http://language.perl.com/info/software.html>.
125
126 - HTML::Element. If you don't have this installed, you can get
127 this from CPAN. Use the command:
128
129 perl -e 'use CPAN; CPAN::install("HTML::Element");'
130
131 You may need to be root to do this.
132
133To create HTML files:
134
135 - Perl 5.6.0 or newer. Find the software at
136 <http://language.perl.com/info/software.html>.
137
138 - LaTeX2HTML 99.2b8 or newer. Older versions are not
139 supported; each version changes enough that supporting
140 multiple versions is not likely to work. Many older
141 versions don't work with Perl 5.6 as well. This also screws
142 up code fragments. ;-( Releases are available at:
143 <http://www.latex2html.org/>.
144
145
146I got a make error: "make: don't know how to make commontex/patchlevel.tex."
147----------------------------------------------------------------------------
148
149Your version of make doesn't support the 'shell' function. You will need to
150use a version which does, e.g. GNU make.
151
152
153LaTeX (or pdfLaTeX) ran out of memory; how can I fix it?
154--------------------------------------------------------
155
156This is known to be a problem at least on Mac OS X, but it has been
157observed on other systems in the past.
158
159On some systems, the default sizes of some of the memory pools
160allocated by TeX needs to be changed; this is a configuration setting
161for installations based on web2c (most if not all installations).
162This is usually set in a file named texmf/web2c/texmf.cnf (where the
163top-level texmf/ directory is part of the TeX installation). If you
164get a "buffer overflow" warning from LaTeX, open that configuration
165file and look for the "main_memory.pdflatex" setting. If there is not
166one, you can add a line with the setting. The value 1500000 seems to
167be sufficient for formatting the Python documetantion.
168
169
170What if Times fonts are not available?
171--------------------------------------
172
173As distributed, the LaTeX documents use PostScript Times fonts. This
174is done since they are much better looking and produce smaller
175PostScript files. If, however, your TeX installation does not support
176them, they may be easily disabled. Edit the file
177texinputs/pypaper.sty and comment out the line that starts
178"\RequirePackage{times}" by inserting a "%" character at the beginning
179of the line. If you're formatting the docs for A4 paper instead of
180US-Letter paper, change paper-a4/pypaper.sty instead. An alternative
181is to install the right fonts and LaTeX style file.
182
183
184What if I want to use A4 paper?
185-------------------------------
186
187Instead of building the PostScript by giving the command "make ps",
188give the command "make PAPER=a4 ps"; the output will be produced in
189the paper-a4/ subdirectory. (You can use "make PAPER=a4 pdf" if you'd
190rather have PDF output.)
191
192
193Making HTML files
194-----------------
195
196The LaTeX documents can be converted to HTML using Nikos Drakos'
197LaTeX2HTML converter. See the Makefile; after some twiddling, "make"
198should do the trick.
199
200
201What else is in here?
202---------------------
203
204There is a new LaTeX document class called "howto". This is used for
205the new series of Python HOWTO documents which is being coordinated by
206Andrew Kuchling <akuchlin@mems-exchange.org>. The file
207templates/howto.tex is a commented example which may be used as a
208template. A Python script to "do the right thing" to format a howto
209document is included as tools/mkhowto. These documents can be
210formatted as HTML, PDF, PostScript, or ASCII files. Use "mkhowto
211--help" for information on using the formatting tool.
212
213For authors of module documentation, there is a file
214templates/module.tex which may be used as a template for a module
215section. This may be used in conjunction with either the howto or
216manual document class. Create the documentation for a new module by
217copying the template to lib<mymodule>.tex and editing according to the
218instructions in the comments.
219
220Documentation on the authoring Python documentation, including
221information about both style and markup, is available in the
222"Documenting Python" manual.
223
224
225Copyright notice
226================
227
228The Python source is copyrighted, but you can freely use and copy it
229as long as you don't change or remove the copyright notice:
230
231----------------------------------------------------------------------
232Copyright (c) 2000-2006 Python Software Foundation.
233All rights reserved.
234
235Copyright (c) 2000 BeOpen.com.
236All rights reserved.
237
238Copyright (c) 1995-2000 Corporation for National Research Initiatives.
239All rights reserved.
240
241Copyright (c) 1991-1995 Stichting Mathematisch Centrum.
242All rights reserved.
243
244See the file "commontex/license.tex" for information on usage and
245redistribution of this file, and for a DISCLAIMER OF ALL WARRANTIES.
246----------------------------------------------------------------------
Note: See TracBrowser for help on using the repository browser.