From 9f03380d1cb5829305750cfcc2ec1cdea18e3311 Mon Sep 17 00:00:00 2001
From: Fred Drake <fdrake@acm.org>
Date: Fri, 19 Feb 1999 22:56:08 +0000
Subject: Use more current approach to recording authors.

---
 Doc/lib/libparser.tex | 9 +++------
 1 file changed, 3 insertions(+), 6 deletions(-)

(limited to 'Doc/lib/libparser.tex')

diff --git a/Doc/lib/libparser.tex b/Doc/lib/libparser.tex
index 80ad493eea..49a92e51f8 100644
--- a/Doc/lib/libparser.tex
+++ b/Doc/lib/libparser.tex
@@ -10,12 +10,13 @@
 %
 
 \section{\module{parser} ---
-         Access parse trees of Python code.}
+         Access parse trees for Python code}
+
 \declaremodule{builtin}{parser}
+\modulesynopsis{Access parse trees for Python source code.}
 \moduleauthor{Fred L. Drake, Jr.}{fdrake@acm.org}
 \sectionauthor{Fred L. Drake, Jr.}{fdrake@acm.org}
 
-\modulesynopsis{Access parse trees of Python source code.}
 
 \index{parsing!Python source code}
 
@@ -27,10 +28,6 @@ to parse and modify an arbitrary Python code fragment as a string
 because parsing is performed in a manner identical to the code
 forming the application.  It is also faster.
 
-The \module{parser} module was written and documented by Fred
-L. Drake, Jr. (\email{fdrake@acm.org}).%
-\index{Drake, Fred L., Jr.}
-
 There are a few things to note about this module which are important
 to making use of the data structures created.  This is not a tutorial
 on editing the parse trees for Python code, but some examples of using
-- 
cgit v1.2.1

