and call it "distutils.cfg" instead of "pydistutils.cfg" (personal
config files are still ".pydistutils.cfg" or "pydistutils.cfg", though).

Look for personal config file in /home/greg on Windows, too: users will have
to set /home/greg to use this, so it's not something that many people will
use.  But if python-dev comes up with the "right way" to divine a
home directory on Windows, we can use that to set /home/greg and poof! --
personal Distutils config files on Windows.

	Fix a small bug in posixmodule.c where a char* is being
	dereferenced where it should not be.

one doesn't *do* anything by default; it's just there as a conduit for data
(eg. include dirs, libraries) from the user to the "build" commands.
However, it provides a couple of Autoconf-ish methods ('try_compile()',
'try_link()', 'try_run()') that derived, per-distribution "config" commands
can use to poke around the target system and see what's available.

Initial experimenst with mxDateTime indicate that higher-level methods are
necessary: analogs of Autoconf's AC_CHECK_HEADER, AC_CHECK_LIB will be
needed too (and that's just to probe the C/C++ system: how to probe the
Python system is wide open, and someday we'll have to worry about probing a
Java system too).

command being reinitialized to false.

Define USE_GUSI2, not USE_GUSI1. PythonStandalone still doesn't compile due to tk issues, though, but it isn't important right now.

Added a CARBON indicator to the version string.

Half-fixed RPM 2 compatibility:added 'rpm_base' option, which must be set
  (to eg. /usr/src/redhat on a stock Red Hat system) if rpm2_mode is on.
  Still not quite working, though.

spelled sensibly in a config file.

Fills in question marks in help

Reads scripts in from files rather than strings

Adds RPM 2 compatibility mode (untested). Use of this mode requires that
--bdist-base be specified because bdist_rpm has no way of detecting where
RPM wants to find spec files and source files. An unmodified RedHat 5.0
system would require '--bdist-base=/usr/src/RedHat'. (You would also have
to be root.) If the rpmrc file has been modified to allow RPMs to be built
by normal users then --build-base would need to be changed accordingly.

Formats the changelog.

GPW: tweaked formatting, added some editorial comments.

and added 'ensure_dirname()'.

command class, so they're now in the Command base class.

(and in order to generate a more sensible error message cleanly).

   from Greg Stein

   (Pointed out by Moshe Zadka)

Wrote Unicode section

overhaul last night.

  support the forthcoming Cygwin/Mingw32 GCC-on-Windows patch.
Standardized CVS id line.

First version of the project that produces a working Carbon binary. The binary has only been tested on MacOS9, so far. This project needs CW IDE 4.1b4 or later.

Revived various of the compatability routines and made them Carbon-compliant. This is needed because the initial carbon-python does not use GUSI.

Removed hfsrunning() macro. This means MacPython won't run on MacOS 5 (oops, System 5) or earlier anymore:-)

Made the core toolbox modules carbon-compatible using the new greylist feature of bgen: non-carbon methods are still included in non-carbon MacPython. The issue of backward compatibility of Python code is still open.
Macmodule and macosmodule have also been carbonified. Some functionality is still missing there.

Replaced GetFInfo and SetFInfo calls with FspGetFInfo and FspSetFInfo calls, which are carbon-compatible.

- Don't call all the toolbox init routines.
- No balloon help, so removed help code from the initial dialog.

- Use TickCount() in stead of LMGetTicks()
- Don't use xxxGetFile event filter
- Don't call SystemTask or HandleSysWindowEvent (is this also automatically handled under os9??)
- Don't scan event queue for cmd-. (to be fixed at some point).

(Temporarily?) removed call to ProcessHighLevelEvent until we find out how to do this (Carbon only).