- Use internal version of finder class so we don't drag in finder
  tools
- error -1704 also ignored during arg unpack
- Use Scriptable Text Editor for example

implement "every", etc.

I found this in a mail of two and a half years ago from Yusuf Goolamabbas.

(In description of AbstractWriter class.)

	      "{\em ...}" ==> "\emph{...}"

	      Not at all sure what to do with "{\rm ...}".
	      Leaving it for now.

	      Always include the comma *inside* the \optional{} markup!

where Make doesn't know that '#' as a command is a comment.

Added \label{} for referring to the module.

"Unix" ==> "\UNIX{}"

Also change the build rules to use $(LIBRARY) instead of
  -L.. -lpython$(VERSION)
since the latter trips up the SunOS 4.1.x linker (sigh).

"Unix" ==> "\UNIX{}"

"C" ==> "\C{}"

"C++" ==> "\Cpp{}"

"Unix" ==> "\UNIX{}"

"C" ==> "\C{}"

"C++" ==> "\Cpp{}"

Added "user configuration file", ".pythonrc.py file" to the index.

Made reference to site module a {seealso} environment.

Added "module search path" to the index.

"Unix" ==> "\UNIX{}"

sys.prefix is no longer empty on any platform that I know of.

times are there as well.

Doing it here means the switch only affects one file and gets everything
rebuilt as needed.

Added -9 option to gzip.  This doesn't save much space, but it's "free" and
appreaciated by those with slow modems.  (With these tarballs, that means
"those with modems"...!)

Remove the two tarballs in the clean target.

so we'll not need this shell whackery after all.

  tarps - one-sided PostScript
  tarps2 - two-sided PostScript, with ref.ps added as-is.
  tardvi - yes, some people want the .dvi files

  all-ps2 - Create the .ps files, but make sure the LaTeX openright option
	    is used in the \documentclass.

for usage information.

	to create a module index in the HTML version.

index.  It works, it's ugly, and would probably have to be completely redone
if we changed latex2html versions.  See the comments.  ;-(

On the other hand, it works.  ;-)

(Wait for myformat.perl checkin as well.)

For all generated cases of <strong>...</strong> (from this module), change to
<b>...</b>.  This, from me?  This is entirely to reduce the size of the
generated markup, which is more of an issue than semantics here.  Since
<strong> isn't very meaningful anyway, this should be good.

Consistently use trailing "()" on function / method names.

Wrapped some long lines.