[issue16309] "PYTHONPATH=" different from no PYTHONPATH at all

Armin Rigo added the comment: Grrr, ok, I have an "alias ls='/bin/ls'". It seems that both "PATH=" and "unset PATH" are equivalent to "PATH=.". This is behavior that we cannot add to PYTHONPATH, I fear, because so far "." is not implicitly included if PYTHONPATH is not set. Or if we do it's

[issue16309] "PYTHONPATH=" different from no PYTHONPATH at all

R. David Murray added the comment: I don't think bin is included: > PATH= gzip bash: gzip: No such file or directory But you are right...unset seems to be equivalent to PATH= I could have sworn it acted different when I tried it, but I just ran it again and it it acted the same, which make

[issue16309] "PYTHONPATH=" different from no PYTHONPATH at all

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:

[issue16309] "PYTHONPATH=" different from no PYTHONPATH at all

Tom Vaughan added the comment: Oh wow. That is not what I remembered/assumed about sh and PATH. Mind. Blown. -- ___ Python tracker ___ ___

[issue16309] "PYTHONPATH=" different from no PYTHONPATH at all

R. David Murray added the comment: Hmm. Although that argues that the original behavior was in fact correct. At least, the behavior of bash and zsh for me is that PATH= foo finds foo if it is in the local directory, contradicting the claim made in the original post. --

[issue16309] "PYTHONPATH=" different from no PYTHONPATH at all

Tom Vaughan added the comment: PATHONPATH=/tmp: will also be interpreted as "/tmp" and ".". Do the patches also address this case? PYTHONPATH=:/tmp and PYTHONPATH=/foo::/bar are also problematic. -- nosy: +tvaughan ___ Python tracker

[issue16309] "PYTHONPATH=" different from no PYTHONPATH at all

R. David Murray added the comment: It may be problematic, but it is also consistent with the way the shell works in general. (Try the same things with PATH.) -- nosy: +r.david.murray ___ Python tracker __

[issue16309] "PYTHONPATH=" different from no PYTHONPATH at all

Roundup Robot added the comment: New changeset 803e5a732331 by Ezio Melotti in branch 'default': #16309: avoid using deprecated method and turn docstring in a comment. http://hg.python.org/cpython/rev/803e5a732331 -- ___ Python tracker

[issue16309] "PYTHONPATH=" different from no PYTHONPATH at all

Andrew Svetlov added the comment: Fixed. Thanks. -- resolution: -> fixed stage: commit review -> committed/rejected status: open -> closed ___ Python tracker ___ ___

[issue16309] "PYTHONPATH=" different from no PYTHONPATH at all

Roundup Robot added the comment: New changeset 05f8f7544f92 by Andrew Svetlov in branch 'default': Issue #16309: Make PYTHONPATH= behavior the same as if PYTHONPATH not set at all. http://hg.python.org/cpython/rev/05f8f7544f92 -- nosy: +python-dev __

[issue16309] "PYTHONPATH=" different from no PYTHONPATH at all

Alexey Kachayev added the comment: Unit test added. pythonpath2.diff is included into issue16309.diff. -- nosy: +kachayev Added file: http://bugs.python.org/file27848/issue16309.diff ___ Python tracker

[issue16309] "PYTHONPATH=" different from no PYTHONPATH at all

Andrew Svetlov added the comment: I would to see some unittest if possible. -- ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue16309] "PYTHONPATH=" different from no PYTHONPATH at all

Changes by Andrew Svetlov : -- nosy: +asvetlov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue16309] "PYTHONPATH=" different from no PYTHONPATH at all

Changes by Chris Rebert : -- nosy: +cvrebert ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue16309] "PYTHONPATH=" different from no PYTHONPATH at all

Changes by Serhiy Storchaka : -- stage: -> commit review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue16309] "PYTHONPATH=" different from no PYTHONPATH at all

Serhiy Storchaka added the comment: LGTM. -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscr

[issue16309] "PYTHONPATH=" different from no PYTHONPATH at all

Eric Snow added the comment: > Given how confusing it seems, perhaps we should change it to > adopt a PATH-like behaviour. Wouldn't that introduce a backward-compatibility issue? FWIW, otherwise I agree that it makes a lot of sense to conform to the same behavior as PATH. -- nosy: +er

[issue16309] "PYTHONPATH=" different from no PYTHONPATH at all

Armin Rigo added the comment: Attached another simpler diff (only one "+" line instead of two...). -- Added file: http://bugs.python.org/file27712/pythonpath2.diff ___ Python tracker ___

[issue16309] "PYTHONPATH=" different from no PYTHONPATH at all

Armin Rigo added the comment: Attached the diff, in case we want to do that. The diff is only about non-Windows platforms, given that it follows a Posix use case about PATH. But do we also need to change PC/getpathp.c? -- keywords: +patch Added file: http://bugs.python.org/file27709/

[issue16309] "PYTHONPATH=" different from no PYTHONPATH at all

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue16309] "PYTHONPATH=" different from no PYTHONPATH at all

Antoine Pitrou added the comment: Given how confusing it seems, perhaps we should change it to adopt a PATH-like behaviour. -- nosy: +pitrou ___ Python tracker ___ _

[issue16309] "PYTHONPATH=" different from no PYTHONPATH at all

New submission from Armin Rigo: On Posix, it is documented that setting PATH to the empty string is equivalent to not setting PATH at all, which is an exception to the rule that in a string like "/bin::/usr/bin" the empty string in the middle gets interpreted as ".". PYTHONPATH does not have t