This bug is for 2.2.1, not 2.2.1 "candidate."

Setup.py in the home directory explains how to obtain
the current version of the expat package. However, it
gives the path to the private home page of the original
developer. The package at that location is incorrect;
the correct package is at
<http://sourceforge.net/projects/expat/>.

The stale package introduces several problems:
* The package does not create the "expat.h" in
/usr/include that setup.py looks for
* The stale package does not automatically create libaries

The correct package fixes both of these problems.

SUGGESTED FIX:

* Modify setup.py to point to correct package. Note:
configure, make, make install will install the correct
libaries and include files.

* Modify README to include information about expat.
Speaking as a user, there's no reason for me to suspect
that I have to read setup.py to find out which modules
might not be included when I compile! Information about
expat belongs in README, so that I understand what
packages might be necessary for me to install before I
run the installation process.

HELP:

If you wish to assign me to rewrite this documentation,
I can do so; I'm a little reluctant to touch setup.py
because I only have a Linux setup here, and touching
any py module means testing across builds IMHO.

Logged In: YES 
user_id=21627

I would appreciate if you could produce a patch (context
diff, please), both for setup.py, and Modules/Setup.

I don't think modifying README is necessary, since the
reader is already directed to read Modules/Setup in README.
If you would like to see specific text, feel free to include
it in your patch.

Please attach the patch to this report.

Logged In: YES 
user_id=3066

The specific problem you cite is no longer a problem with
the descriptions in our working sources.

I've made additional updates of the descriprion in setup.py
1.94 and 1.73.4.6.