1. Only .py files were getting installed.
2. Empty CVS directories were getting created.
Both were due to trying to get away with "recursively copy *.py" one-
liner scripting.

Still need to test it in pathological scenarios.

the installation was hiding in a part of the GUI I never saw before.  Add
it.

don't use directly, but the Wise utility scripts we invoke (like
uninstal.wse) sometimes need them.

not in the stuff we inherited from Wise 5.0 -- better safe than sorry.

Got rid of useless "Welcome" screen.
Folded Tcl/Tk into the main Python component.
Bug introduced during upgrade:  Start Menu entries didn't work if
    installation was to a path with an embedded space, because the
    enclosing quotes somehow got dropped on the cmdline args.  Repaired.
Years of wizard-generated code blocks left this script hard to read.
    Added many more comments, blank lines, and rearranged related code
    into related blocks where they had drifted apart.
Added %_PYMAJOR_% and %_PYMINOR_% compiler vrbls, and reworked script
    items to use them as appropriate.  This should slash the amount of
    hand-fiddling needed when version numbers change.  Indeed, in the
    body of the script, only the first line should need changing now.
Deleted unreferenced wizard-generated compiler vrbls.

"relative paths" option is enabled, 8.1 rewrites *every* path to be
relative to PCbuild (the dir containing the .wse script), even absolute
paths you type in by hand, paths to the Wise installation itself, and even
paths to the Windows directories (sheesh).  Only way to stop it is to
start a path with a variable reference, and we screwed ourselves before
by not using the predefined %_WISE_% vrbl to point to the Wise
installation.  Repaired that old, repeated and well-hidden mistake.
Also:
+ Got rid of the %_SRC_% vrbl (such paths always relative to PCBuild now).
+ Changed the %_DOC_% vrbl to prompt for the location of the unzipped
  HTML files (defaults to ..\html, cuz that's where I put them, but I
  expect I'll change that later cuz I always hated mixing the generated
  docs into the CVS tree ... Guido, if you're reading this, where did you
  unpack the docs when building a Windows installer?  Happy to oblige.).
+ Stopped the generated installer from filling up the entire screen (got
  rid of the massive blue background gradient -- new option).
+ Added the helpful app publisher and app URL registry entries that Win2K
  displays in its version of Add/Remove.

the old script without any complaints, didn't demand any manual changes,
and built a working installer from it that acts very much like the old one.
It did add a few script items, and changed one, so checking it in now
before I break everything again.

until you download the new expat and install it; see PCbuild\readme.txt.

list of files to not extract docstrings from when the -D option is
given.  This isn't optimal, but I didn't want to change the semantics
of -D, and it's bad form to allow optional switch arguments.

Bumping __version__ to 1.4.

TokenEater.__init__(): Initialize __curfile to None.

__waiting(): In order to extract docstrings from the module, both the
    -D flag should be set, and the __curfile should not be named in
    the -X filename (i.e. it isn't in opts.nodocstrings).

set_filename(): Fixed a bug where once the first module docstring is
    extracted, no subsequent module docstrings will be extracted.  The
    bug was that the first extraction set __freshmodule to 0, but that
    flag was never reset back to 1.  set_filename() is always called
    when the next file is being processed, so use it to reset the
    __freshmodule flag.

main(): Add support for -X/--no-docstring.

special cases.  test_pkg works again on Windows.

d:/whatever instead of /whatever.  While I'm afraid changing isabs()
to be *consistent* with this would break lots of code, it makes
best sense for join() to do it this way.  Thanks to Alex Martelli for
pushing back on this one!

list.

Present the URLs at the bottom in a consistent manner, conforming to the
style guide.

Remove the lone use of "e.g.", which the style guide does not allow.

It's guaranteed now, assuming the platform modf() works correctly.

surrogates for Unicode code points outside range(0x10000) on narrow
Python builds.

Code by Evan Simpson.

to the current Python interpreter (ie. the one used for
building/installation), even (especially!) if "/usr/bin/env" appears in
the #! line.

Rationale: installing scripts with "#!/usr/bin/env python" is asking for
trouble, because
  1) it might pick the wrong interpreter (not the one used to
     build/install the script)
  2) it doesn't work on all platforms (try it on IRIX 5, or on Linux
     with command-line options for python)
  3) "env" might not be in /usr/bin

do it back in copy_file() (not at module level).

wide builds.

and fixes bug #438786.