[issue15533] subprocess.Popen(cwd) documentation: Posix vs Windows

Eryk Sun added the comment: > I don't understand the wording proposed (that seem backwards to me?) Thanks. Looks like I inverted the logic of the quoted paragraph. It should have been a "relative path with a slash in it" is resolved against the current working directory, not "without a

[issue15533] subprocess.Popen(cwd) documentation: Posix vs Windows

ban added the comment: >> "In particular, the function looks for executable (or for the >> first item in args) relative to cwd if the executable path is >> a relative path." > > For POSIX, this should be stated as a "relative path without a slash in > it" or a "relative path without a

[issue15533] subprocess.Popen(cwd) documentation: Posix vs Windows

Gregory P. Smith added the comment: For our subprocess docs, Eryk's text: """ For POSIX, ``executable`` should be stated as a "relative path without a slash in it" or a "relative path without a directory in it". An unqualified filename is a relative path that won't be resolved against

[issue15533] subprocess.Popen(cwd) documentation: Posix vs Windows

Eryk Sun added the comment: > Python is conceptually multi-platform, so its behavior on > Linux and Windows should be as much consistent as possible. It's not expected for the behavior of all Popen() parameters to be the same on all platforms. For example, the behavior and capabilities of

[issue15533] subprocess.Popen(cwd) documentation: Posix vs Windows

Change by Gregory P. Smith : -- assignee: -> gregory.p.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue15533] subprocess.Popen(cwd) documentation: Posix vs Windows

Change by Chris Jerdonek : -- assignee: chris.jerdonek -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue15533] subprocess.Popen(cwd) documentation: Posix vs Windows

Jan Lachnitt added the comment: Nobody responds yet, so I will. I think that the basic proposal was made by Chris Jerdonek in msg171692 already on 2012-10-01: First document both behaviors and then discuss the possible harmonization. I think the proposal was good and further discussion has

[issue15533] subprocess.Popen(cwd) documentation: Posix vs Windows

Gregory P. Smith added the comment: Thanks for pointing me at this issue Ned. It sounds like there is a behavior difference between Windows and POSIX systems related to the current directory and/or which process environment is used by the system call that launches the new process to find

[issue15533] subprocess.Popen(cwd) documentation: Posix vs Windows

Change by Ned Deily : -- nosy: +gregory.p.smith versions: +Python 3.8 -Python 3.5 ___ Python tracker ___ ___ Python-bugs-list

[issue15533] subprocess.Popen(cwd) documentation: Posix vs Windows

Damon Atkins added the comment: >From https://msdn.microsoft.com/en-us/library/windows/desktop/ms682425.aspx Note Python is using CreateProcess(), consider using CreateProcessW() The Unicode version of this function, CreateProcessW, can modify the contents of this string. Therefore, this

[issue15533] subprocess.Popen(cwd) documentation: Posix vs Windows

Jan Lachnitt added the comment: @eryksun: Sorry for my late reply, apparently I did not have time to reply in 2017. I see your point, but still I think that Python is conceptually multi-platform, so its behavior on Linux and Windows should be as much consistent as possible. I am not the

[issue15533] subprocess.Popen(cwd) documentation: Posix vs Windows

Damon Atkins added the comment: See also https://bugs.python.org/msg262399 -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue15533] subprocess.Popen(cwd) documentation: Posix vs Windows

Damon Atkins added the comment: I see from this. That this is still an issue https://github.com/python/cpython/blob/master/Lib/subprocess.py#L1146 Is it not a solution to save current directory location chdir(cwd) before calling _winapi.CreateProcess() restore the original directory. This

[issue15533] subprocess.Popen(cwd) documentation: Posix vs Windows

Eryk Sun added the comment: The Unix implementation of subprocess.Popen follows the behavior of os.execvpe, which is an outlier. Other execvpe implementations, such as the one added to glibc in 2009, search PATH in the current environment instead of the passed environment. As such, and given

[issue15533] subprocess.Popen(cwd) documentation: Posix vs Windows

Changes by Martin Panter : -- components: +Windows stage: test needed -> needs patch title: subprocess.Popen(cwd) documentation -> subprocess.Popen(cwd) documentation: Posix vs Windows ___ Python tracker