[issue16309] "PYTHONPATH=" different from no PYTHONPATH at all
Armin Rigo
report at bugs.python.org
Fri Apr 12 20:55:27 CEST 2013
Armin Rigo added the comment:
Uh, confusion. Indeed, "PATH= foo" finds foo in the current directory on bash. I'm not sure how I ran the original example. It seems that a default PATH is used, which includes at least "/bin" and ".".
The point I was making in the original post is still valid: "PATH= foo" appears to behave identically to "unset PATH && foo" in all cases I tried so far. For example, for me both work with some local executable or with "ls" (which is in /bin), and neither works with "which" (which is in /usr/bin).
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue16309>
_______________________________________
More information about the Python-bugs-list
mailing list