After updating Roundup, run_tests.py won't work anymore; see attached
patch.  Perhaps related to recent refactoring of setup.py?

This command (testing anypy, issue 2550503) worked before; running the
specific test directly still works.

Python 2.6.1, Windows XP; same problem for Python 2.3, 2.4, 2.5
(sys.path varying); for Python 2.4, it has worked for me before (with
2.3, run_tests.py won't work for me because I don't have a win32con for it)

Yes, I have noticed that dependency, too. However, I'm not sure what the
right thing to do is, as I'm unconvinced that running this
'check_manifest()' function as a test is such a good idea.
First, it requires Roundup to be built (and thus should be disabled when
run in the source tree), and second, the same function is run during the
build procedure itself, too.

In fact, I'm not sure I see the need for this function at all. As it
compares existing files with the files from MANIFEST (a file that itself
has been built by listing existing files matching some glob pattern), it
seems a bit redundant.
Richard, do you have an opinion on this ? Can thie check_manifest()
function go ?

Patch, reflecting refactored directory structure

After being told that several '*.~' files are 'missing', I decided
check_manifest() is just the wrong function to call from within
run_tests.py, and so I removed it with rev:4173. 
(It may make sense as part of the build, but even there I'm not fully
convinced. But this is for another issue, another day...)