This appears to be a bug in upstream setuptools, not in the Debian/Ubuntu
packaging. I earlier thought that I had confirmed that it did *not* happen with
pristine setuptools, but just now I tried to reproduce it and it happens with
pristine setuptools. Also a Debian developer tried to reproduce it on his
Debian-sid/lenny system and the problem did not manifest there!
This appears to be a bug in upstream setuptools, not in the Debian/Ubuntu
packaging. I earlier thought that I had confirmed that it did *not* happen with
pristine setuptools, but just now I tried to reproduce it and it happens with
pristine setuptools. Also a Debian developer tried to reproduce it on his
Debian-sid/lenny system and the problem did not manifest there!
I suspect that it might have something to do with bugs.python. org/setuptools/ issue20
http://