On 05/06/2011 04:43 PM, Carl Meyer wrote: > I don't quite understand this. On my Ubuntu system, with either Ubuntu's > Python 2.6 or my compiled 3.2, sys.path[0] appears to always be the > empty string, never the actual full path of the script's directory. How > is it ever == '/usr/share/pyshared' for you?
Eh, never mind - guess it uses the actual directory when you provide a script file to run, instead of running interactively. I never knew that. > I was going to say that for a slightly less Debian-specific form of > paranoia, could we only delete sys.path[0] if its in fact the empty > string? But there seems to be something I'm still missing. Alternatively, could we actually follow the paths ourselves and ensure the path that's being removed is the location of virtualenv.py? I'd just rather not have the Debian-specific version of the fix in virtualenv. Or, if sys.path[0] being the script's directory is an absolute guarantee, we could just skip the paranoia entirely? Carl _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
