using "python -m doctest [-v] filename ...".

lost that tests are sorted by name before being run.  ``DocTestFinder``
has been changed to sort the list of tests it returns.

argument.  A lot of hair went into supporting that!

Remove various dependencies on dictionary order in the standard library
tests, and one (clearly an oversight, potentially critical) in the
standard library itself - base64.py.

Remaining open issues:
 * test_extcall is an output test, messy to make robust
 * tarfile.py has a potential bug here, but I'm not familiar
   enough with this code.  Filed in as SF bug #1496501.
 * urllib2.HTTPPasswordMgr() returns a random result if there is more
   than one matching root path.  I'm asking python-dev for
   clarification...

Contributed by Bjorn Tillenius.

stdout arguments, making it possible to redirect input and output
for remote debugging.

shouldn't create a new flag when `name` is already the name of
an option flag.

Edward Loper.

to work correctly with modules imported from zipfiles or via other PEP 302
__loader__ objects.  Tests and doc updates are included.

Patch by Ilya Sandler.

Bugfix candidate.

this is useful for locating supporting data files, just as it is in Python
modules

trace_dispatch() result in a more obvious, and more robust way.

showing that doctest's pdb.set_trace() support was dramatically broken.

doctest.py _OutputRedirectingPdb.trace_dispatch():  Return a local trace
function instead of (implicitly) None.  Else interaction with pdb was
bizarre, noticing only 'call' events.  Amazingly, the existing set_trace()
tests didn't care.

non-ascii characters.

request.  Tim says that "correct 'fuzzy' comparison of floats cannot
be automated."  (The motivation behind adding the new option
was verifying interactive examples in Python's latex documentation;
several such examples use numbers that don't print consistently on
different platforms.)

the expected output to match corresponding number literals in the
actual output if their values are equal (to ten digits of precision).

the process of writing docs for the other "missing" debug support
functions.

"soon", after I repair the LaTeX I somehow damaged.

unittest support function, from the public interface.  If they're not
documented, they shouldn't be public.

and the LaTeX docs are in increasingly good shape.

- Simplified code to find names for file-based tests.

  all examples in a given text file. (analagous to "testmod")
- Minor docstring fixes.
- Added module_relative parameter to DocTestFile/DocTestSuite, which
  controls whether paths are module-relative & os-independent, or
  os-specific.

  - Fixed bug in handling of absolute paths.
  - If run from an interactive session, make paths relative to the
    directory containing sys.argv[0] (since __main__ doesn't have
    a __file__ attribute).

with default False for testmod().  The real point of introducing this was
so that output from doctest.master.summarize() would be the same as in
2.3, and doctest.master in 2.4 is a backward-compatability hack used only
by testmod().

controls whether tests are included for objects with empty docstrings.
Defaults to True, to match the behavior of Python 2.3.

doctest always promised to stick "__test__" in the name.  That got
broken.  Now it's fixed again.

the "backward compatibility" here was a joke.

was passed.

in the new docs.

DocTestRunner.__run:  Separate the determination of the example outcome
from reporting that outcome, to squash brittle code duplication and
excessive nesting.