Guido, you should probably look at this.  The pickle documentation is out of
date; I don't see anything about the __reduce__() stuff or the
__safe_for_unpickling__ attribute.

index references the appropriate RFCs.

Consistency:  Always use trailing "()" on function names in running text.

is based on the line above, watch out for landing inside a triple
quoted string.  In this case, use iterative search +
parse-partial-sexp backwards to find the beginning of the string.

Note this does affect performance, but very little in the common cases
(I hope).  It could be made *much* faster by adding Emacs and XEmacs
dependent code -- different code naturally.  :-(

Fixes the following reported bug:

if len(sys.argv) >= 6:
    # More lines here
    fptr = open('/etc/hosts', 'w')
    fptr.write("""# /etc/hosts -- autocreated by /etc/ppp/ip-up
#
# Address from pppd
%-15s	%s

# For loopbacking
127.0.0.1	localhost

255.255.255.255	broadcast
""" % (ipaddr, ipname) )

os.chmod('/etc/hosts', 0644)

file local variable section of a file.  When set, and the user hits
C-c C-c, this file gets executed instead of the buffer's file.  Idea
given by Roy Dragseth <royd@math.uit.no>, but implemented differently.

(py-execute-buffer): Support py-master-file variable.  If this names a
relative path, default-directory is prepended via expand-file-name.

Use trailing "()" on function names in running text.

normal modules portion of the manual, but that's the basic effect of this
section with the 1.5 change in exception support.

tables:  \var{}

Add a couple of index entries to the File Objects section.

Marked title of the Python Reference Manual as \emph{}, like other Python
manual titles.

	These are intended to support semantic markup.  There are a number
	of places in the documentation where the exact meaning of an
	indentifier marked \code{} in the running text is ambiguous (could
	be a module or a class, a function or a method, etc.).  These are
	intended to clarify the intent of the identifier for processing
	applications and more intelligent style processing.

"--" ==> "---"

it already got it right.

	      isn't likely to be of much interest these days....)

{\tt ...} ==> \code{...}

Added \label{module-blat} for the two supporting modules.

Added index entries for referred-to modules.

standard Python API function so it should not have a Py prefix.

Also documented that groups() now always returns a tuple.

- added docstrings
- support option to specify a different purported directory name
- reindented with 4 spaces

would set the transfer to text mode instead of the specified mode.

    HTTP/1.x 200
instead of
    HTTP/1.x 200 OK

the error was about a bad format string :-).

contains the type of the object and name of the attribute.

'\377' for EOF.

executable files, and directories.  When expecting a module, we also
look for the .pyc or .pyo file.

1.3, dlopen() etc. are fully implemented, including dlerror().
From Jaromir Dolecek and Ty Sarna.

to do, it should not call sys.exitfunc either...

- fix type_to_name(); it never worked
- add path_to_selector()
add path_to_datatype_name()

now implement the following finalization strategy.

1. Whenever this code deletes a module, its directory is cleared
   carefully, as follows:
   - set all names to None that begin with exactly one underscore
   - set all names to None that don't begin with two underscores
   - clear the directory

2. Modules are deleted in the following order:
   - modules with a reference count of 1, except __builtin__ or __sys__
   - repeat until no more are found with a reference count of 1
   - __main__ if it's still there
   - all remaining modules except __builtin__ or sys
   - sys
   _ __builtin__

Added an optional third parameter giving the purported filename for
error messages from the module.

Append a newline to the code string if needed.