[Python-Dev] disable writing .py[co] (original) (raw)

Skip Montanaro skip@pobox.com
Tue, 21 Jan 2003 07:47:14 -0600 

Michael> The idea of writing .pycs to a world writable area (say /tmp)
Michael> on a multi-user system sounds like a Bad Thing.

As I mentioned in my original note, you'd prepend PYCROOT to the .py file and append 'c' to create a filename for the .pyc file. If socket.py was found in /usr/lib/python2.3/socket.py and PYCROOT was set to /tmp, you'd try to read from/write to /tmp/usr/lib/python2.3/socket.pyc. The only requirement on PYCROOT would be that /tmp would have to exist. The user wouldn't be responsible for creating the full directory tree underneath /tmp.

Skip