Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
08c5d0cd
Commit
08c5d0cd
authored
Sep 11, 2000
by
Fred Drake
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add documentation for the \pep and \seepep macros.
parent
526a1823
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
21 additions
and
6 deletions
+21
-6
Doc/doc/doc.tex
Doc/doc/doc.tex
+21
-6
No files found.
Doc/doc/doc.tex
View file @
08c5d0cd
...
...
@@ -534,6 +534,13 @@ distribution, to create or maintain whole documents or sections.
\var
{
option
}
.
\end{macrodesc}
\begin{macrodesc}
{
pep
}{
\p
{
number
}}
A reference to a Python Enhancement Proposal. This generates
appropriate index entries. The text
\samp
{
PEP
\var
{
number
}}
is
generated; in the HTML output, this text is a hyperlink to an
online copy of the specified PEP.
\end{macrodesc}
\begin{macrodesc}
{
refmodule
}{
\op
{
key
}
\p
{
name
}}
Like
\macro
{
module
}
, but create a hyperlink to the documentation
for the named module. Note that the corresponding
...
...
@@ -811,13 +818,21 @@ distribution, to create or maintain whole documents or sections.
document (the corresponding
\macro
{
declaremodule
}
is required).
\end{macrodesc}
\begin{macrodesc}
{
see
rfc
}{
\p
{
number
}
\p
{
title
}
\p
{
why
}}
Refer to an
IETF Request for Comments (RFC
).
\var
{
number
}
should be the official number assigned by the
RFC
Editor,
\var
{
title
}
should be the human-readable title of the
RFC
as
\begin{macrodesc}
{
see
pep
}{
\p
{
number
}
\p
{
title
}
\p
{
why
}}
Refer to an
Python Enhancement Proposal (PEP
).
\var
{
number
}
should be the official number assigned by the
PEP
Editor,
\var
{
title
}
should be the human-readable title of the
PEP
as
found in the official copy of the document, and
\var
{
why
}
should
explain what's interesting about the RFC. This should be used
to refer the reader to RFCs which specify protocols or data
explain what's interesting about the PEP. This should be used
to refer the reader to PEPs which specify interfaces or language
features relevant to the material in the annotated section of the
documentation.
\end{macrodesc}
\begin{macrodesc}
{
seerfc
}{
\p
{
number
}
\p
{
title
}
\p
{
why
}}
Refer to an IETF Request for Comments (RFC). Otherwise very
similar to
\macro
{
seepep
}
. This should be used
to refer the reader to PEPs which specify protocols or data
formats relevant to the material in the annotated section of the
documentation.
\end{macrodesc}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment