[issue20927] Different behaviour on Posix and Windows when using subprocess.Popen(..., cwd=path)

Jovik added the comment: I appreciate your suggestion regarding cygwin, but in the new code base we want to avoid this dependency. Thanks for your time on this issue. -- ___ Python tracker <http://bugs.python.org/issue20

[issue20927] Different behaviour on Posix and Windows when using subprocess.Popen(..., cwd=path)

Jovik added the comment: Isn't Python's crossplatform functionality a key feature? A quick fix would be to retry the call by adding cwd to arg[0] in case of FileNotFoundError. -- ___ Python tracker <http://bugs.python.o

[issue20927] Different behaviour on Posix and Windows when using subprocess.Popen(..., cwd=path)

Jovik added the comment: Why this feature works on Posix systems, but not Windows? If my memory is correct, it didn't work anywhere when I used Python 2.7 (according with docs). -- ___ Python tracker <http://bugs.python.org/is

[issue19643] shutil rmtree fails on readonly files in Windows

Jovik added the comment: This could be at least part of docs; I found that people tend to avoid shutil.rmtree(...) on Windows because of such issues. Some of them call subprocess("rmdir /S /Q ") to get desired behavior. -- nosy: +Jovik

[issue20927] Different behaviour on Posix and Windows when using subprocess.Popen(..., cwd=path)

Jovik added the comment: plink.exe is located in c:\python33\workspace. I'm aware of the docstring difference between Python 2 and 3, thus submitted the bug for Python 3 only. -- ___ Python tracker <http://bugs.python.org/is

[issue20927] Different behaviour on Posix and Windows when using subprocess.Popen(..., cwd=path)

Jovik added the comment: As requested I did extra tests with extension. Same result as before: >>> proc = subprocess.Popen("plink.exe", stdout=subprocess.PIPE, >>> cwd="c:\\python33\\workspace") >>> proc = subprocess.Popen(".\plink.exe",

[issue20927] Different behaviour on Posix and Windows when using subprocess.Popen(..., cwd=path)

Jovik added the comment: I'm quite aware of the os.sep issues between the systems, but I checked both out of curiosity. Here are latest results: All of the following commands raises the same exception: >>> proc = subprocess.Popen("plink", stdout=subprocess.PIPE

[issue20927] Different behaviour on Posix and Windows when using subprocess.Popen(..., cwd=path)

Jovik added the comment: I did a test with cwd being set to full path, but the result was the same (still had to use shell=True to execute a command). Let me know if I can provide any more details. -- ___ Python tracker <http://bugs.python.

[issue20927] Different behaviour on Posix and Windows when using subprocess.Popen(..., cwd=path)

New submission from Jovik: This works on Linux as expected: import subprocess proc = subprocess.Popen(["./app"], stdout=subprocess.PIPE, cwd="workspace") but on Windows I get: FileNotFoundError: [WinError 2] The system cannot find the file specified To successfully execute

[issue16521] logging.basicConfig creates empty file when using handlers

New submission from Jovik: Using logging.basicConfig() with Python 3.2.3 accepts handlers options without any errors. It creates an empty file. I don't think this should be default behaviour, sice it's very missleading (no exception thrown; no warning on standard output or i