Logged In: YES 
user_id=6405

The manifest messages are not fatal, so may be ignored. I don't 
know why the MANIFEST isn't being included - the MANIFEST.in 
file specifically has "include run_tests.py *.txt demo.py 
MANIFEST.in MANIFEST". The MANIFEST file contains a line 
"MANIFEST". I just re-bundled the code, and the MANIFEST file is 
in there - it's just not in the version on sf.net's download area. 
 
When building, I specifically perform separate steps: 
 
 python setup.py clean --all 
 python setup.py sdist --manifest-only 
 python setup.py sdist --quiet 
 
... so I really don't know WTF is going on :( 
 
BTW, the setup.py "build" command is not necessary. 
 
Having said all that, I've just tested both "build" and "install" 
using Python 2.3.4 and the tarball from the files section on 
https://sourceforge.net/project/showfiles.php?group_id=31577 
and it works fine for me. 
 
I guess I'll just be more alert next time I bundle a release, and 
check for the MANIFEST file in the release...