http://www.tortall.net/mu/blog/2005/12/01

Pointed out from SF #1365916.

Backport candidate.

(calling ftell(stdin) doesn't seem defined).  So we won't test errors
from ftell unless we can do it portably.

using the Python implementations of the functions. This imcreases code
coverage and makes sure that both implementations do the same thing.

  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.