svn:ignore *.pyc *.pyo
  svn:eol-style native

The .py files appear to have been checked in with Windows or inconsistent line
endings.  The current check-in disrupts the 'svn blame', but hopefully it is
irrelevant for freshly imported code.

Supresses numerous pages of compiler warnings.

comment based on 'sys.args[0]' does not depend on the path.  For Python
builds from a remote directory ("/path/to/configure; make") the previous
logic used to include the "/path/to" portion in Python-ast.h.  Then svn
would consider this file to be locally modified.

- add file I forgot to add in previous commit

test that package, not the xmlcore/PyXML switcheroo fiasco in the xml
module/package

added missing API hooks

(e.g. cStringIO, ucnhash, etc)

files on the platform.

ftell(3) on BSD doesn't set errno even for ttys and returns useless
values.

  * Remove talk of shell scripting, replacing it by some more current examples
  * Mention C++ and Java as well as C

Raymond H., please feel free to rewrite or revert as you see fit.
If the changes are OK, they could be backported to the 2.4-maint branch.

 make sure xml.etree can be used even if PyXML is present
 (solution proposed by Philip J. Eby)

 added xml.etree documentation stub

make sure that all included components work)

 assorted xml.etree tweaks

build problem on AIX.

Strip off leading dots and slash so the generated files are the same regardless
of whether you configure in the checkout directory or build.

If anyone configures in a different directory, we might want a cleaner
approach using os.path.*().  Hopefully this is good enough.

If a line had multiple semi-colons and ended with a semi-colon, we would
loop too many times and access a NULL node.  Exit the loop early if
there are no more children.

In C++, it's an error to pass a string literal to a char* function
without a const_cast().  Rather than require every C++ extension
module to put a cast around string literals, fix the API to state the
const-ness.

I focused on parts of the API where people usually pass literals:
PyArg_ParseTuple() and friends, Py_BuildValue(), PyMethodDef, the type
slots, etc.  Predictably, there were a large set of functions that
needed to be fixed as a result of these changes.  The most pervasive
change was to make the keyword args list passed to
PyArg_ParseTupleAndKewords() to be a const char *kwlist[].

One cast was required as a result of the changes:  A type object
mallocs the memory for its tp_doc slot and later frees it.
PyTypeObject says that tp_doc is const char *; but if the type was
created by type_new(), we know it is safe to cast to char *.

This enables even impatient people to run tests that require remote
files such as test_normalization and test_codecmaps_*.

meaningless numbers, but I figured out I would fix that bug anyway.