Fixed problems when unpickling in restricted execution environments.
These methods try to assign to an instance's __class__ attribute, or
access the instances __dict__, which are prohibited in REE.  For the
first two methods, I re-implemented the old behavior when assignment
to value.__class__ fails.

For the load_build() I also re-implemented the old behavior when
inst.__dict__.update() fails but this means that unpickling in REE is
semantically different than unpickling in unrestricted mode.

a copy of the defaults dictionary and merges the section's dictionary
into it so that sections can override the defaults.

	      calling the Python API.

demo, so here it is.

Removed " (byte code instruction)" from the output of the {opcodedesc}
environment; this should only appear in the index (which it now does).

Removed some really old cruft related to otherwise removed debugging code.
(I *think* assignments to $* set & clear auto-flush of <STDOUT>, but don't
really remember.  Removing them seems to not change anything!)

	any changes introduced there.  Also ensure a little more space between
	the module name and the parenthesized comment.

Clarified that floor() and ceil() return reals.  Same for the integer part
returned by modf().

Some markup consistency changes.

importantly, \url{}.

constructs should be used.

semantic concepts.

Added two new ones (not discussed with Guido:

\constant{}:  Markup for constants defined in Python modules.

\cfunction{}:  Markup for C functions; these should probably be distinguished
	by font, but are not at this time (since they're typically \code{} at
	this point).

continuation lines.  This fixes this bug report, reported by Frank
Stajano.

# But if I split the "raise" line and reindent, the else WRONGLY goes up a
# level (?!?)

while condition1:
    if condition2:
        raise error3, \
              moreInfo4
else: # meant to close "if condition2"
    action5()

a religious issue: RMS decrees that the Enter (RET) key should just do
a newline and a LFD (C-j) should do a newline and indent (i.e. the
python-mode version of this).  Almost everyone I know disagrees and
finds that RET should do newline and indent.  Almost everyone hacks
their modes to do this, if they know how.  Because it's hard for
newbies to figure out how to do this, and because most DOS keyboards
lack a LFD (leaving users to the more obscure C-j), I think it makes
better sense to add this default binding.

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.