On Thu, Jun 17, 2010 at 12:19 AM, Denis Jasselette
What OS are you using and which set of commands did you exactly use ?
I am using Ubuntu 10.04 (python 2.6). And here is what I did:
$ ll -rwxr-xr-x 1 denis denis 396 2010-06-16 14:39 setup.py -rwxr-xr-x 1 denis denis 10K 2010-06-16 14:13 teqhtml -rw-r--r-- 1 denis denis 203 2010-06-16 14:11 teqhtml_config.py $ ./setup.py build [...] $ sudo ./setup.py install [...] $ ll /usr/local/bin/ -rwxr-xr-x 1 root root 10K 2010-06-16 17:06 teqhtml $ ll /usr/local/lib/python2.6/dist-packages/ -rw------- 1 root staff 281 2010-06-16 17:06 teqhtml-0.5.egg-info -rw------- 1 root staff 203 2010-06-16 14:11 teqhtml_config.py -rw------- 1 root staff 562 2010-06-16 17:06 teqhtml_config.pyc
Actually, install doesn't change permissions, they are set while building. It looks like the umask is taken into account for py_modules but permissions are explicitly changed for scripts. If I set my umask to 0000 for instance, I don't have that problem.
What is your umask (when the .py are non world-readable) ? I believe sudo has a different way of handling umask (compared to using straight root account). You could try installing as root instead of using sudo, and/or checking your sudoers for umask settings, David