module.  Closes patch #675551.  My apologies to Michal Vitecek for taking so
long to process this.

warning from GCC.  Closes patch #1006629.

Cherniavsky Beni!

top-down.  Now matches the PEP.

of the pdb.Pdb class gives have been corrected. d(own) goes to a newer frame,
u(p) to an older frame, not the other way around.

path, as normalizing the path may alter the meaning of the path if it contains
symlinks.

Also add tests for infinite symlink loops and parent symlinks that need to be
resolved.

exist.

symbolic links. This has been documented in a comment since 1992, but is now in
the library reference as well.

onto a link to itself. Thanks Gregory Ball.

symbolic link (bug #851123 / patch #854853, thanks Gregory Ball).

test_format/test_unicode in some circumstances (patch #1007539/bug #992078).

reached through a symlink (was comparing path of module to path to function and
were not matching because of the symlink).  os.path.realpath() is now used to
solve this discrepency.

Closes bug #570300.  Thanks Johannes Gijsbers for the fix.

them (which they are now), I had to rewrite the code to understand
it.  This has got to be the most DWIM part of doctest -- but in context
is really necessary.

Backport candidate

the remaining data in the buffer (which it had done happily without reporting
any results)

this depends on a new feature in Expat added in 1.95.8

There were subsections without sections, so drop a sub.

implemented, just what it does.

are documented now, and ripped out a bunch of "private name" convolutions.

default 1MB to 2 million bytes.  The test suite passes with -uall again
(test_compiler no longer drives WinXP into an insane state).

to a file.

[ 1005891 ] support --with-tsc on PPC

plus a trivial change to settscdump's docstring and a Misc/NEWS entry.

[ 1004703 ] Make func_name writable

plus fixing a couple of nits in the documentation changes spotted by MvL
and a Misc/NEWS entry.

habit of these, sorry).

[ 1005248 ] new.code() not cleanly checking its arguments

using the result of new.code() can still destroy the sun, but merely
calling the function shouldn't any more.

I also rewrote the existing tests of new.code() to use vastly less
un-bogus arguments, and added tests for the previous insane behaviours.